AWS Lambda vs. Rackspace Managed Hosting

Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.

Incentivized

Rackspace is very well suited as a IaaS (Infrastructure as a Service) provider, particularly when you're planning on leaving the infrastructure up for a period of time. They seem to focus a bit more on that aspect of infrastructure. That is to say, they seem to promote running servers for longer periods of time and not spinning up/shutting down servers frequently based on usage spikes. While, they do support that sort of availability -- they don't have features built into their offering, necessarily, that make it a lot easier to implement. Our experiences with Rackspace have been 100% around their cloud platform, but they have another entire part of their business that is centered around hosting/maintaining/supporting physical hardware (bare metal). They have had a great reputation over the last several years (10+) for being top-notch providers in this space, which is one reason we even considered them for our Cloud-based hosting needs. We don't have any direct experience with their "bare metal" offerings, but their reputation is certainly great, and worth noting.

Incentivized

• No provisioning required - we don't have to pay anything upfront
• Serverless deployment - it gets executed only when request comes and we pay only for the time the request is getting executed
• Integrates well with AWS CloudWatch triggers so it is easy to setup scheduled tasks like cron jobs

Incentivized

• Fanatical Support - I can't stress how great their team is. Not only are they knowledgeable, whenever I call in (during the day or in the middle of the night), I never have to wait more than a minute to speak to someone.
• Webmail, Hosted Exchange, and Office365 Support - As an IT team of one, Rackspace's cloud solution and migration team has really helped me over the years to minimize issues for users, but also provide a reliable and flexible email platform.

Incentivized

• Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
• For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
• Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
• Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.

Incentivized

• Latest outage 12/2/22 and counting over 75 hours - in my opinion, support has been miserable. In my experience, there's little/no communication regarding the problem or cause. No support. In my opinion, erroneous advice. Virtually NOTHING for users. I feel we've been abandoned.
• Outage appears to have been caused by unpatched servers & no backup servers
• In my opinion, NO COMPANY should trust their data or services to a nonresponsive company like Rackspace.
• In my experience, there are NO published policies/practices re: server maintenance (patching) to mitigate hacking, NO published policies/practices re: backup servers in the event of problems. I feel it's stupid of me as a user to have chosen to trust them with critical services

If I wake tomorrow completely incapable of managing a client cloud operation, our dedicated Rackspace Cloud Engineering Team is deployable as literal extension of our business, immediately addressing all needs and requirements without cause of business disruption for our consultancy, and more importantly for the mission-critical ones of our clients. For this reason alone, Rackspace is our choice of choices!

Incentivized

I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.

Incentivized

The company does not put as much focus on usability as other cloud competitors and it is kind of clear. It would be good to take a quarter and gather intense feedback, and then another quarter and focus purely on UI enhancements and backend interoperability

Incentivized

Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.

Incentivized

In my experience, their support team is massively overworked — taking FOUR DAYS to look at tickets, and a MONTH to fix problems!

Incentivized

AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions

Incentivized

LiquidWeb or Amazon both offer some products that could be considered similar. I will say though, after years of dealing with Rackspace, their service is what always has me coming back. Their support is typically so much better than other vendors that I hesitate to use other vendors. Pricing might be cheaper, but when you have an issue and need it resolved ASAP, then Rackspace has come through in the majority of cases for me.

Incentivized

• Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
• Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
• Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.

Incentivized

• We've found it helpful to host our own web sites on their cloud servers, which is a positive.
• We've also hosted our Nagios instance on a low-end cloud server, which is also a positive.
• A negative impact is that they've now decided to start charging for their support.

Incentivized