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).
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
DigitalOcean App Platform
Score 8.0 out of 10
N/A
The DigitalOcean App Platform enables developers to build, deploy, and scale apps on what they describe as a simple, fully managed PaaS.
Users of the former Nanobox, acquired by DigitalOcean in 2019, have been migrated to the App Platform upon Nanobox's end of life in March 2021.
$5
per month
Pricing
AWS Elastic Beanstalk
DigitalOcean App Platform
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Basic
$5
per month
Professional
$12
per month
Offerings
Pricing Offerings
AWS Elastic Beanstalk
DigitalOcean App Platform
Free Trial
No
No
Free/Freemium Version
Yes
Yes
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
DigitalOcean App Platform
Features
AWS Elastic Beanstalk
DigitalOcean App Platform
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
AWS Elastic Beanstalk is well suited for [the] rapid development of applications that use standard compute platforms based on popular programming languages. So getting a Go, Python, Ruby, or Node.js app going in AWS Elastic Beanstalk will be easy. For non-standard applications, containers provide another option for using AWS Elastic Beanstalk. In either case, AWS Elastic Beanstalk is well suited for applications that are [self-contained]. AWS Elastic Beanstalk is also good for development or test environments that need a built-in deployment method. AWS Elastic Beanstalk is less appropriate for complex applications that rely on multiple AWS services. While deploying and running the base code might be easy to get going, it may be difficult to apply permissions and integrations with the other services.
It can help you to host your virtual appliance or serverless application at very low cost. DigitalOcean marketplace also helps you to deploy the serverless app or virtual appliance effortlessly. It is suitable for small-scale deployment and the process to set up an account and rolling out your app via the marketplace is easy and cheap.
How to more easily integrate with other other AWS services. There are plenty out there, but it's not quite as seamless as I feel like it should be to mix and match products.
Make backing up easier when scaling the server. It took quite a bit of time to make sure we had everything set up in case something went wrong.
When you are first starting to use AWS, the dashboard can be very intimidating. There are countless products all with names that aren't very indicative of what they actually do.
The company has not been very communicative as of lately. Not much news, no apparent work on missing features.
Some components are incomplete as far as some critical features. For example, I use RethinkDB as my database and it's missing critical features like backup and clustering, so It is unusable and they should have made that clear from the get go.
The pricing on the support plan is vague. I do have the feeling it is actually well worth the money, but it's hard to form a decisions based without more predictable specific.
Seems to me like the platform's future is unclear.
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.
There are many services like AWS Elastic beanstalk, but there are none with the maturity in the platform or the cost-effectiveness of AWS Elastic Beanstalk. Also, AWS Elastic Beanstalk is the oldest among them, so there are more people with AWS experience than the other platforms. The only thing is their documentation and UX are a bit old, which doesn't stop it from performing greatly, but yes, if you are looking for better UX, then you can check out other options.
The ability to choose your own cloud provider is huge, especially for a small start up like I have. We have a lot of free credit from AWS, Google Cloud, IBM, Azure, etc... The data layer is baked into the system which is better for integration then an external provider. There are also a lot fewer differences between environment as everything is Docker based which gives me the confidence that what works on my machine is going to work in production. Heroku doesn't have good support for Docker containers yet and although Heroku has served me well in the past, it is limited in some aspects.
Elastic Beanstalk removes countless hours from development team responsibility, freeing up those resources to instead focus on building the products that our customers want to use.
As a business that is already embedded into using EC2 instances, it's essentially free to leverage the work that AWS performs on configuring the Elastic Beanstalk stacks.
With Elastic Beanstalk, while there is still a responsibility to ensure that applications can work with updated underlying dependencies, it's much easier when AWS handled the heavy lifting of updating the stacks.
