Posts Tagged ‘scaling’
In this blog post I’m going to cover how we are scaling our engineering department at LeaseWeb: where we started, the lessons we’ve learned, and how we are hoping to move forward. LeaseWeb was founded in 1997 and we currently have over 350 employees throughout the world with the majority working at our headquarters in Amsterdam. The engineering department currently has about 100 employees and manages 65,000 servers in seven locations (with more to be added soon).
In the past development was based on shifting priorities rather than planned business cases. Developers weren’t able to concentrate their efforts on thoroughly building, testing, documenting, and presenting a demo for one project before another more urgent one was moved to the head of the line. Operations and Development were working on different schedules and weren’t able to meet each other’s requirements to their mutual satisfaction. We wanted to change this.
In this 2-part mini-series, Joshua Hoffman examines some of the common issues companies face when designing for scalability. Read part 1 here.
In my previous blog I looked at what I call the first three sins of web scale – pride (the refusal to use tools not invented here), envy (the desire for a more exciting project) and gluttony (ignoring scope and capacity). Today I’ll discuss the other four sins you need to be aware of when building and deploying your app or product. So without further ado, let’s check them out.
Throughout my career I’ve had the opportunity to work at a variety of different companies both large and small. They each had their own set of unique challenges regarding growth but one thing I noticed with time and experience was that the solutions to the problems they faced were not specific to the company itself. The approaches that were taken and the lessons that were learned could be extrapolated and applied to many of the situations facing a company looking to expand and grow technically.
There is a concept in some religions that before you save a sinner you have to tell them how they have sinned. In other words, if someone doesn’t know what the problem is they won’t be able to change. For a company just starting out, there are no wrong ways to build and deploy your app or product. Once you begin to grow however, you realize there are things you didn’t know and that some or all of the decisions that you made at the beginning were mistakes. This is the point where you need to decide how to address these issues. New companies are started all the time so I decided to draw from my experience to put together what I call the Seven Deadly Sins of Web Scale using seven real world examples from my career.
Over the last few years, cloud-based business solutions have fundamentally changed the way we do business on nearly every level, offering unprecedented mobility, accessibility and storage. The global business landscape still presents challenges, however, as businesses learn how to integrate current systems and harness the power of the cloud to its fullest capacity.
At LeaseWeb, we know that businesses experience a wide variety of triumphs and trials when it comes to managing resources and scaling to demand. That’s why we’re going beyond just the “good” in this blog post and talking about what we’ve seen our customers really experience.
We’ve had a busy few months in the cloud team. In March this year, we launched the virtual network-backed Cloud product – giving customers the opportunity to use a private internal network to communicate between cloud instances. The advantages are obvious – free data traffic, easy scaling, and protected private traffic within your cloud. After the release, we worked on adding a load balancing functionality to the virtual network and software-defined firewall to make it easier for customers to balance and scale traffic. Last Wednesday, we released this functionality to all our Public Cloud customers – giving them the option to add a load balancer to their infrastructure via our Customer Portal.