3 ms·
Well, they explained it clearly in blog post: https://github.com/blog/493-github-is-moving-to-rackspace https://github.com/blog/493-github-is-moving-to-rackspac
by strzalek 15y ago
Well, they explained it clearly in blog post: https://github.com/blog/493-github-is-moving-to-rackspace https://github.com/blog/493-github-is-moving-to-rackspace
- jabo 15y agoThanks for the link, but in that article they mention why they moved from Engine Yard to Rackspace. My question was why they didn't move to ec2 from Engine Yard.
- dcousineau 15y agoI would imagine their bullet point about flexibility and direct hardware access is why Rackspace won over EC2. I've used both ends of Rackspace (colo and cloud) and would imagine it would be simple to utilize both services under a common support account (which is Rackspace's big upsell: their support). EC2 doesn't even have a colo option or partner so you'd have to roll your own solution. Better to take advantage of the integration considdering price is close enough.