Beanstalk is migrating to colocation


Since Beanstalk started, weve been through a long evolution of changes in our server infrastructure. The very first Beanstalk deployment was on a Media Temple grid server. With limited resources, that obviously did not last long. We then moved to Softlayer, where we had a few physical servers that ran our infrastructure. Back then, we did not really have the experience to manage servers, security and performance on our own. Shortly after, a nice opportunity came up to host with Engine Yard as a partner. This was a perfect fit, because they managed the infrastructure and left the application to us. They helped us grow during our first year and provided amazing support. As we grew however, we realized that in order to maintain a reliable and fast service, we needed to be accountable for our infrastructure.

Growing a product requires an understanding of the entire stack to really get what you want from it, and that is just what we did when we moved to Rackspace. It allowed us to choose our hardware, isolate services and troubleshoot on our own to understand our capacity and growth requirements. Weve been happily hosting with Rackspace since July of 2009.

In the last month however, weve made a big decision to move Beanstalk to colocation, a data center where we purchase the hardware and manage just about everything. Im going to cover some of the reasons why we made this decision, along with some information on the hardware and provider we chose.

Read More

Khash Sajadi

Khash is the founder and CEO of Cloud 66, a full stack container management as a service. Follow him on @khash

London, UK and San Francisco, US
Subscribe and get updates

Have feedback? Please get in touch @cloud66 on Twitter.

Everything you need to build, manage and maintain containers in production on your own servers and any cloud

Try Cloud 66 — 14 Days Free Trial, No credit card required