AWS Elastic Beanstalk is the platform-as-a-service offering provided by Amazon and designed to leverage AWS services such as Amazon Elastic Cloud Compute (Amazon EC2), Amazon Simple Storage Service (Amazon S3).
$35
per month
Rackspace Managed Hosting
Score 1.1 out of 10
N/A
Rackspace Managed Hosting is cloud computing company Rackspace's managed IT services and IaaS offering. Its infrastructure options include bare metal servers, virtual single-shared servers, and cloud multi-tenant environments.
$23
per month
Pricing
AWS Elastic Beanstalk
Rackspace Managed Hosting
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
I selected these solutions because they are the closest to being able to set up separate server or VM instances. As far as performance and scalability, Heroku does offer an autoscale option, but the base cost to have the autoscale in place, sets Heroku behind EBS. Digital …
Heroku - In order to transfer files to Heroku, you need to know how to use GIT. The flexibility to define how you transfer files to a Rackspace server has its advantages. However, the autoscale ability of Heroku sets it above Rackspace.
I have been using AWS Elastic Beanstalk for more than 5 years, and it has made our life so easy and hassle-free. Here are some scenarios where it excels -
I have been using different AWS services like EC2, S3, Cloudfront, Serverless, etc. And Elastic Beanstalk makes our lives easier by tieing each service together and making the deployment a smooth process.
N number of integrations with different CI/CD pipelines make this most engineer's favourite service.
Scalability & Security comes with the service, which makes it the absolute perfect product for your business.
Personally, I haven't found any situations where it's not appropriate for the use cases it can be used. The pricing is also very cost-effective.
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.
Getting a project set up using the console or CLI is easy compared to other [computing] platforms.
AWS Elastic Beanstalk supports a variety of programming languages so teams can experiment with different frameworks but still use the same compute platform for rapid prototyping.
Common application architectures can be referenced as patterns during project [setup].
Multiple environments can be deployed for an application giving more flexibility for experimentation.
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.
Limited to the frameworks and configurations that AWS supports. There is no native way to use Elastic Beanstalk to deploy a Go application behind Nginx, for example.
It's not always clear what's changed on an underlying system when AWS updates an EB stack; the new version is announced, but AWS does not say what specifically changed in the underlying configuration. This can have unintended consequences and result in additional work in order to figure out what changes were made.
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
As our technology grows, it makes more sense to individually provision each server rather than have it done via beanstalk. There are several reasons to do so, which I cannot explain without further diving into the architecture itself, but I can tell you this. With automation, you also loose the flexibility to morph the system for your specific needs. So if you expect that in future you need more customization to your deployment process, then there is a good chance that you might try to do things individually rather than use an automation like beanstalk.
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!
It is a great tool to manage your applications. You just need to write the codes, and after that with one click, your app will be online and accessible from the internet. That is a huge help for people who do not know about infrastructure or do not want to spend money on maintaining infrastructure.
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
As I described earlier it has been really cost effective and really easy for fellow developers who don't want to waste weeks and weeks into learning and manually deploying stuff which basically takes month to create and go live with the Minimal viable product (MVP). With AWS Beanstalk within a week a developer can go live with the Minimal viable product easily.
- Do as many experiments as you can before you commit on using beanstalk or other AWS features. - Keep future state in mind. Think through what comes next, and if that is technically possible to do so. - Always factor in cost in terms of scaling. - We learned a valuable lesson when we wanted to go multi-region, because then we realized many things needs to change in code. So if you plan on using this a lot, factor multiple regions.
We also use Heroku and it is a great platform for smaller projects and light Node.js services, but we have found that in terms of cost, the Elastic Beanstalk option is more affordable for the projects that we undertake. The fact that it sits inside of the greater AWS Cloud offering also compels us to use it, since integration is simpler. We have also evaluated Microsoft Azure and gave up trying to get an extremely basic implementation up and running after a few days of struggling with its mediocre user interface and constant issues with documentation being outdated. The authentication model is also badly broken and trying to manage resources is a pain. One cannot compare Azure with anything that Amazon has created in the cloud space since Azure really isn't a mature platform and we are always left wanting when we have to interface with it.
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.
