GitHub's Architecture, before and after migration

http://www.anchor.com.au/blog/2009/09/github-designing-success/

by quellhorst • 17 years ago

80 14 17 years ago

anchor.com.au

wmf• 17 years ago

Are we to believe that Rackspace plus outsourced system administration is still cheaper than Engine Yard? Impressive.

cmelbye• 17 years ago

Engine Yard hosting was free. I don't think it was about cutting costs necessarily, but rather it was for improving the performance of the site and opening opportunities for scaling rapidly in the future.

simonk2• 17 years ago

EY told them if they wanted to continue to start paying and they said it was a different by a huge amount.

nakajima• 17 years ago

I'd argue no, at least until you have as good an idea of what your needs are as GitHub did.

qhoxie• 17 years ago

The move to Rackspace will bring about a new backend architecture and a lot more servers, leading to a much improved user experience for everyone. - TPW from Github

I don't believe that cost was an issue for them with EY. It was about their system's needs regarding server resources.

datums2• 17 years ago

I've setup similar solutions in the past. Nowadays I don't agree with having an entire stack basically sitting idle. I prefer to get those resource involved intelligently. Looking forward to more details and possible reasons for choosing the technology (DRDB, LB software, etc )

mojombo• 17 years ago

We run 12GB of memcache on each slave file server. Hardly idle!

datums2• 17 years ago

I was looking at http://www.anchor.com.au/blog/wp-content/uploads/2009/09/Git... which shows file server B as a failover, traffic coming into the active LB. Does the active LB then have a pool which includes other file server B services ?

pilif• 17 years ago

Their migration seems to have gone quite smoothly. And the whole site feels much faster to me.

Congratulations for that.

And thanks for sharing this information about your architecture, this was a very interesting read.

colinprince• 17 years ago

Only 1TB+ of storage for 15+ physical servers?

murrayb• 17 years ago

I've used Anchor for web hosting (for myself & for clients) and I thoroughly recommend them. Not only is their service great they have technically competent staff. The norm in IT these days seems to be that you have to persevere/fight your way through x layers of support before you get someone who understands tech, at Anchor everytime the person who first spoke to me was able to understand and resolve the issue.

GitHub's Architecture, before and after migration

Related Stories