Re:GitHub's Architecture, before and after migration
by wmf on Sunday September 27, 2009 @11:41PM
(#847716)
Are we to believe that Rackspace plus outsourced system administration is still cheaper than Engine Yard? Impressive.
[ Parent
| on HN ]
Re:GitHub's Architecture, before and after migration
by qhoxie on Monday September 28, 2009 @12:15AM
(#847769)
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.
Re:GitHub's Architecture, before and after migration
by cmelbye on Monday September 28, 2009 @12:11AM
(#847761)
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.
Re:GitHub's Architecture, before and after migration
by simonk on Monday September 28, 2009 @12:14AM
(#847765)
EY told them if they wanted to continue to start paying and they said it was a different by a huge amount.
Re:GitHub's Architecture, before and after migration
by tumult on Monday September 28, 2009 @12:40AM
(#847795)
It's not that simple. EY's filesystem stuff is designed for read-almost-always, as you would expect for most Rails sites. GitHub does a lot of writing. Growing GitHub's setup would have been a huge undertaking for EY (from what I've read of their posts) and you just can't do that stuff for free, or you run out of money.
(This is just what I've gleaned from comments. They parted ways amicably. Don't stir up drama.)
Re:GitHub's Architecture, before and after migration
by simonk on Monday September 28, 2009 @12:42AM
(#847799)
Yes, but you can't say if they stayed at EY it would be free.