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 Fabric
Score 6.3 out of 10
N/A
A solution to bring cloud security, billing, operations and management together. Rackspace Fabric offers a single platform for automated multicloud management. Service includes access to Rackspace cloud technology expertise, and provides a unified interface management for all cloud resources across Azure, AWS, GCP, and VMware, in a single, SaaS like operating environment.
$500
per month
Pricing
AWS Elastic Beanstalk
Rackspace Fabric
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Minimum Service
$500.00
per month
Offerings
Pricing Offerings
AWS Elastic Beanstalk
Rackspace Fabric
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS Elastic Beanstalk
Rackspace Fabric
Features
AWS Elastic Beanstalk
Rackspace Fabric
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
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.
I am highly likely to recommend Rackspace Cloud Monitoring to a colleague. This is assuming they have a decent background in working on cloud servers. If you don't mind digging in yourself to solve problems, then this is a great resource. If you are just learning how to set up servers on your own, then I recommend at least hiring someone to help you use the service. With that being said, Rackspace makes it easy for people you may hire to seamlessly work within your account. They get their own separate developer account.
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.
Immediate email notifications: In case a service is down on our servers, we get immediate email notifications via rackspace cloud monitoring service. This helps us to know about the issues and we get in contact with support team to get it resolved.
Configuration on specific services: We can configure this monitoring on specific services. So for example if i don't want to get notified if MySQL concurrent users limit reached, then I do not need to configure this monitoring for MySQL. I can just use it whenever needed for defined services.
Group emails and technical contacts emails: The monitoring service can send email alerts to a number of email addresses. Primarily the ones who are added as a technical contact. It helps all people get notified about any issue.
Auto ticket management: Rackspace automatically creates a support ticket when a service is down and is notified by their monitoring service.
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.
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.
The overall usability is good enough, as far as the scaling, interactive UI and logging system is concerned, could do a lot better when it comes to the efficiency, in case of complicated node logics and complicated node architectures. It can have better software compatibility and can try to support collaboration with more softwares
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.
I also used Monitis as a monitoring service for our server. Rackspace'S monitoring sends immediate notifications while Monitis might take a couple minutes to understand if a service is down. Since Rackspace has their monitoring integrated with their support system, it helps us a lot and we don't need to call support all the time.
