AWS Elastic Beanstalk vs. CloudFoundry

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
AWS Elastic Beanstalk
Score 9.1 out of 10
N/A
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
CloudFoundry
Score 7.1 out of 10
N/A
CloudFoundry is a free, open source cloud computing platform supported by the non-profit CloudFoundry. It is not tied to any particular cloud service, but can be self-hosted or run on any cloud service preferred.N/A
Pricing
AWS Elastic BeanstalkCloudFoundry
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
No answers on this topic
Offerings
Pricing Offerings
AWS Elastic BeanstalkCloudFoundry
Free Trial
NoNo
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
AWS Elastic BeanstalkCloudFoundry
Top Pros
Top Cons
Features
AWS Elastic BeanstalkCloudFoundry
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
AWS Elastic Beanstalk
9.6
28 Ratings
16% above category average
CloudFoundry
9.8
1 Ratings
18% above category average
Ease of building user interfaces10.018 Ratings10.01 Ratings
Scalability9.928 Ratings9.01 Ratings
Platform management overhead9.727 Ratings00 Ratings
Workflow engine capability9.622 Ratings00 Ratings
Platform access control9.427 Ratings00 Ratings
Services-enabled integration9.827 Ratings00 Ratings
Development environment creation9.627 Ratings10.01 Ratings
Development environment replication9.628 Ratings10.01 Ratings
Issue monitoring and notification9.327 Ratings00 Ratings
Issue recovery9.625 Ratings10.01 Ratings
Upgrades and platform fixes9.526 Ratings10.01 Ratings
Best Alternatives
AWS Elastic BeanstalkCloudFoundry
Small Businesses
AWS Lambda
AWS Lambda
Score 8.8 out of 10
AWS Elastic Beanstalk
AWS Elastic Beanstalk
Score 9.1 out of 10
Medium-sized Companies
IBM Cloud Private
IBM Cloud Private
Score 9.5 out of 10
AWS Elastic Beanstalk
AWS Elastic Beanstalk
Score 9.1 out of 10
Enterprises
IBM Cloud Private
IBM Cloud Private
Score 9.5 out of 10
AWS Elastic Beanstalk
AWS Elastic Beanstalk
Score 9.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
AWS Elastic BeanstalkCloudFoundry
Likelihood to Recommend
9.8
(28 ratings)
10.0
(1 ratings)
Likelihood to Renew
7.9
(2 ratings)
-
(0 ratings)
Usability
7.7
(9 ratings)
-
(0 ratings)
Support Rating
8.0
(12 ratings)
-
(0 ratings)
Implementation Rating
7.0
(2 ratings)
-
(0 ratings)
User Testimonials
AWS Elastic BeanstalkCloudFoundry
Likelihood to Recommend
Amazon AWS
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.
Read full review
CloudFoundry
It's well suited if:
  • The organization has large number of applications that needs to be deployed frequently.
  • The organization is tied to the DevOps mindset.
  • The organization has programs in different languages.
  • The applications does not need EJB's support that servers like web logic provide.
It's less suited if:
  • The applications needs security configuration within the same CloudFoundry instance.
  • The organization, for whatever reason does not want developers to manage the instances.
Read full review
Pros
Amazon AWS
  • 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.
Read full review
CloudFoundry
  • Support for Orgs and Spaces that allow for managing users and deployables within a large organization.
  • Easy deployment, deploying code is as simple as executing single line from CLI, thanks to build-packs.
  • Solid and rich CLI, that allows for various operations on the instance.
  • Isolated Virtual Machines called Droplets, that provide clean run time environment for the code. This used to be a problem with Weblogic and other application servers, where multiple applications are run on the same cluster and they share resources.
  • SSH capability for the droplet (isolated VM's are called droplets), that allows for real time viewing of the App code while the application is running.
  • Support for multiple languages, thanks to build-packs.
  • Support for horizontal scaling, scaling an instance horizontally is a breeze.
  • Support for configuring environment variable using the service bindings.
  • Supports memory and disk space limit allocation for individual applications.
  • Supports API's as well as workers (processes without endpoints)
  • Supports blue-green deployment with minimal down time
Read full review
Cons
Amazon AWS
  • 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.
Read full review
CloudFoundry
  • Does not support stateful containers and that would be a nice to have.
  • Supports showing logs, but does not persist the logs anywhere. This makes relying on Cloud Foundry's logs very unreliable. The logs have to be persisted using other third party tools like Elk and Kibana.
Read full review
Likelihood to Renew
Amazon AWS
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.
Read full review
CloudFoundry
No answers on this topic
Usability
Amazon AWS
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.
Read full review
CloudFoundry
No answers on this topic
Support Rating
Amazon AWS
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.
Read full review
CloudFoundry
No answers on this topic
Implementation Rating
Amazon AWS
- 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.
Read full review
CloudFoundry
No answers on this topic
Alternatives Considered
Amazon AWS
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.
Read full review
CloudFoundry
While Docker shines in providing support for volumes and stateful instances, Cloud foundry shines in providing support for deploying stateless services. Heroku shines in integrating with Git and using commits to git as hooks to trigger deployments right from the command line. But it does not provide on-premise solution that Cloud foundry provides.
Read full review
Return on Investment
Amazon AWS
  • till now we had not Calculated ROI as the project is still evolving and we had to keep on changing the environment implementation
  • it meets our purpose of quick deployment as compared to on-premises deployment
  • till now we look good as we also controlled our expenses which increased suddenly in the middle of deployment activity
Read full review
CloudFoundry
  • Positive impact, since it simplifies the deployment time by a huge margin. Without cloud foundry, deploying a code needs coordination with infrastructure teams, while with cloud foundry, its a simple one line command. This reduces the deployment time from at least few hours to few minutes. Faster deployments promote faster dev cycle iterations.
  • Code maintenance such as upgrading a Node or Java version is as simple as updating the build-pack. Without cloud foundry, using web logic, the specific version only supports a specific version of Java. So updating the version involves upgrading the version of web logic that needs to involve few teams. So without cloud foundry, it takes at least few days, with cloud foundry, its a matter of few mins.
  • Overall, happier Developers and thats harder to quantify.
Read full review
ScreenShots