3 ms·
Disclaimer: my company was acquired by Rackspace 2 years ago. I am a developer myself and below are my honest impressions (and things I have learend) of Rackspa
by old-gregg 12y ago
Disclaimer: my company was acquired by Rackspace 2 years ago. I am a developer myself and below are my honest impressions (and things I have learend) of Rackspace cloud.
Back when they launched it after having had acquired Slicehost, Rackspace Cloud was the only alternative to AWS and had one significant differentiator back then: the local storage on the instances wasn't ephemeral - it was permanent. The benchmarks and pricing were competitive, so the growth was phenomenal and life was good as a result. And that's when Rackspace dropped the ball by losing some focus and getting obsessed with launching platform services one after another ignoring the compute. They even launched what I believe was the first PaaS ever and gave it an unfortunate name of "cloud sites" (and confusing plenty of developers at that point, who couldn't tell "cloud sites", significantly less powerful service, apart from "cloud servers")
As a result, for a few years the lineup of VMs they offered hasn't changed, while AWS was launching new types all the time.
So about two years ago Rackspace ended up with a great control panel (easiest cloud CP to use IMO), a comprehensive set of back-end services: block storage, object storage, MySQL-as-a-Service, email sending and receiving, MongoDB-as-a-Service, cloud deployments, CDN and many more... But the selection of virtual servers was small and the hardware was getting obsolete at that point.
Since then I've seen tremendous investments being made into the core: the compute. Rackspace launched "performance" line of VMs. They still feature persistent (backed by RAID-10 SSDs) local storage, latest Xeons and ridiculously performant network. In a way it's "advantages of backwardness" at work: the performance line of compute is all fresh latest&greatest gear: the servers, the networks, etc. The performance, particularly on disk I/O, is awesome. I hope they'll keep the ball rolling by keeping it up to date by launching new generations in time.
Moreover, Rackspace hired (or acquired) some brainy engineers out of Bay Area who've pushed for "at scale" compute offering which is now called OnMetal (http://rackspace.com/onmetal http://rackspace.com/onmetal) - because that's how internet giants internally do compute, container-based architectures without virtualization, running on highly specialized high-uptime servers (open compute). So... Rackspace cloud today is the only way to experience "facebook-style" infrastructure by renting it by the minute.
The culture of "true web scale" infrastructure is very strong internally, that's why Rackspace has been a huge supporter and believer of Docker, and some Rackers - having grown tired of the sad state of Linux distribution - founded CoreOS (http://coreos.com http://coreos.com), the fresh look at running massively scalable infrastructure from the operating system point of view. Today, Rackspace is the only cloud where you can run Docker containers on top of CoreOS natively on highly efficient (performance per dollar) instantly-provisioned OpenCompute gear without noisy cpu/disk/network neighbors and without virtualization tax.
What could be better?
Well... Rackspace is not the cheapest for undersized deployments [1]. They've never been known for doing things like selling the over-provisioned VMs running on the cheapest machines on consumer-grade SSDs in RAID-5 arrays. A typical Rackspace customer treats a server outage as a big deal, "engineering for failure" for many (most?) cases is actually more expensive than just outsourcing reliability into a higher quality infrastructure. They love to make everything redundant and tend to go with higher spec and high-MTBF parts. Another component of the higher pricing is the support organization. The culture of bending backwards to make customers happy is insane, here's an example: if a customer asks for help resolving problems with Sendgrid (a competing email sending service), Rackspace support people will gladly assist, without bothering them with showing off the superiority of Mailgun - my company Rackspace acquired. I was blown away by that, customer gets help with whatever they feel like getting it.
You can even go as far as asking Rackspace to just run certain components of your infrastructure for you, saving on Devops positions. That's their bread&butter.
While Rackspace offers alternatives to most AWS services, they're not 1-to-1 equivalents. CBS (alternative to EBS) is vastly superior in my opinion because (based on what I know about EBS from public sources) CBS is simpler, has been delivering more predictable and higher performance/uptime experience, Cloud Files (S3 alternative) is comparable, ObjectRocket (MongoDB-as-a-Service) is absolutely phenomenal - the only DBaaS I can recommend anywhere, but there're no Redshift or Glacier counterparts.
I guess what I'm saying is this: Rackspace Cloud has evolved into a grown up contender with a solid feature set matched only by AWS, with multiple DCs all over the world and some unique capabilities (like OnMetal flavor of cloud servers), which differentiates by over-investing into hardware infrastructure and support. So if those qualities matter, take a look. The program Jesse is announcing only makes it easier for you.
[1] Once you cross $10K/mo hosting spend, they're very competitive especially when you factor in the cost of running/managing the infrastructure.
- unoti 12y ago> Rackspace Cloud was the only alternative to AWS and had one significant differentiator back then... One other big differentiator compared to AWS, and the reason I went to Rackspace in the first place: straightforward pricing. Figuring out how much an AWS machine was going to cost was, back then at least, like trying to figure out how much it'd cost to buy a hundred Yen next Monday, for someone who has no experience with currency markets. Amazon's pricing was very complex, but with Rackspace, it was easy for me to tell how much a month would cost for what I needed. > if a customer asks for help resolving problems with Sendgrid (a competing email sending service), Rackspace support people will gladly assist... I was blown away by that, customer gets help with whatever they feel like getting it. While the uptime and performance of the machines I have on Rackspace has been great, the "fanatical support" claim is empty marketing B.S. in my personal experience. A year ago, I had a machine's performance tank while my startup's traffic started to simultaneously ramp up. It turned out there was another host on the same machine slurping too much disk resources, they moved it away. That improved things some, but I ended up needing an expert to take a look at my Apache configuration. I begged Rackspace to help. My startup's life was hanging in the balance: traffic was going up, and performance was going down. I desperately needed help from an expert, and asked Rackspace for help, and offered to pay. They did nothing for me. I started researching it for myself, and basically trained myself to be much more of an Apache configuration expert over the next 48 hours. I needed help, I had money, I was super desperate, and they did nothing for me. I guess the real problem was that I didn't need help with SendGrid, or perhaps I couldn't figure out the right people to ask.
- jnoller 12y agoYou should not have had that apache problem and not gotten help. Period. That's unacceptable, and I'm sorry. We're working on it
- snowwrestler 12y agoOverall I've been a happy Rackspace customer for years, but we've had the same experience with Apache troubleshooting. The support ended at whether Apache was up and running. Beyond that we were told Rackspace considered it to be "application tuning"--which covers all the important settings that are used to manage loads and secure Apache. Luckily a development company we had on contract had a great Linux admin who could help us out. From this perspective Rackspace definitely has not performed a devops role for us. Network administrator? System administrator? Yes, absolutely, and great support for both. But devops is where the application meets the server, and IME Rackspace has stayed away from that. I do see the reason for it--what does Rackspace know about our application? It's not fair to hold them responsible for that. But it created a gap in our professional support. edit: words