AWS Elastic Beanstalk vs. Mirantis Kubernetes Engine

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
AWS Elastic Beanstalk
Score 8.9 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
Mirantis Kubernetes Engine
Score 9.3 out of 10
N/A
The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters on any infrastructure: public cloud, private cloud, or bare metal.
$500
per year per node
Pricing
AWS Elastic BeanstalkMirantis Kubernetes Engine
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Free
$0.00
per year
Basic
$500.00
per year
Offerings
Pricing Offerings
AWS Elastic BeanstalkMirantis Kubernetes Engine
Free Trial
NoYes
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional DetailsThese pricing options are compatible with Linux or Windows Server and are per year, per node. The basic version requires maximum online purchase not to exceed 50 nodes. Support/professional services are not included.
More Pricing Information
Community Pulse
AWS Elastic BeanstalkMirantis Kubernetes Engine
Considered Both Products
AWS Elastic Beanstalk

No answer on this topic

Mirantis Kubernetes Engine
Chose Mirantis Kubernetes Engine
Doocker lacks a lot of the scaling, automation, integration of 3rd party tools/solutions, and integration of shared high-performance self-healing storage, solutions like Heketi provide those missing pieces.
Chose Mirantis Kubernetes Engine
Docker as a local-development-environment is drastically superior to Vagrant, since devs only need to run a single virtual machine. Machine resources go a lot farther.

Docker allows our developers to have a develop/deployment experience very similar to what they would have on Her…
Top Pros
Top Cons
Features
AWS Elastic BeanstalkMirantis Kubernetes Engine
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
AWS Elastic Beanstalk
9.5
28 Ratings
15% above category average
Mirantis Kubernetes Engine
-
Ratings
Ease of building user interfaces10.018 Ratings00 Ratings
Scalability9.928 Ratings00 Ratings
Platform management overhead9.727 Ratings00 Ratings
Workflow engine capability9.522 Ratings00 Ratings
Platform access control9.227 Ratings00 Ratings
Services-enabled integration9.727 Ratings00 Ratings
Development environment creation9.427 Ratings00 Ratings
Development environment replication9.428 Ratings00 Ratings
Issue monitoring and notification9.027 Ratings00 Ratings
Issue recovery9.425 Ratings00 Ratings
Upgrades and platform fixes9.326 Ratings00 Ratings
Best Alternatives
AWS Elastic BeanstalkMirantis Kubernetes Engine
Small Businesses
AWS Lambda
AWS Lambda
Score 8.8 out of 10
Portainer
Portainer
Score 9.3 out of 10
Medium-sized Companies
IBM Cloud Private
IBM Cloud Private
Score 9.5 out of 10
IBM Cloud Kubernetes Service
IBM Cloud Kubernetes Service
Score 9.2 out of 10
Enterprises
IBM Cloud Private
IBM Cloud Private
Score 9.5 out of 10
IBM Cloud Kubernetes Service
IBM Cloud Kubernetes Service
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
AWS Elastic BeanstalkMirantis Kubernetes Engine
Likelihood to Recommend
9.8
(28 ratings)
8.3
(37 ratings)
Likelihood to Renew
7.9
(2 ratings)
9.1
(1 ratings)
Usability
7.7
(9 ratings)
8.0
(2 ratings)
Support Rating
8.0
(12 ratings)
7.8
(3 ratings)
Implementation Rating
7.0
(2 ratings)
-
(0 ratings)
User Testimonials
AWS Elastic BeanstalkMirantis Kubernetes Engine
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
Mirantis
[Mirantis Cloud Native Suite (Docker Enterprise)] is the most advanced tool till now, which works as a VMs
and separates any single application from the dependencies. Also, this tool is
helping me in the agile development of the processes. It is strongly recommended to
almost all major organizations.
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
Mirantis
  • Containers - Docker is the go-to when using Containers, which are super useful if you need an environment that works both for Windows and Linux
  • Efficiency - Docker is very lightweight and doesn't demand too much from your CPU or server
  • CI/CD - Docker is excellent for plumbing into your build pipeline. It integrates nicely, is reliable, and has an easy set up.
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
Mirantis
  • Containers are often opaque - if a container doesn't work out of the box, it's messy to fix.
  • Logging is complexified by the multiple containers and logs are often not piped to places you expect them to be.
  • Networking is complexified due to internal port mapping between containers, etc.
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
Mirantis
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
Mirantis
Docker's CLI has a lot of options, and they aren't all intuitive. And there are so many tools in the space (Docker Compose, Docker Swarm, etc) that have their own configuration as well. So while there is a lot to learn, most concepts transfer easily and can be learned once and applied across everything.
Read full review
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
Mirantis
The community support for Docker is fantastic. There is almost always an answer for any issue I might encounter day-to-day, either on Stack Overflow, a helpful blog post, or the community Slack workspace. I've never come across a problem that I was unable to solve via some searching around in the community.
Read full review
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
Mirantis
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
Mirantis
We've used XAMPP, PHPmyAdmin and similar local environments (our app is on PHP). Because of how easy you can change the configuration of libraries on PHP and versions (which is SO painful on XAMPP or other friendly LAMP local servers) we are using Docker right now. Also, being sure that the environment is exactly the same makes things easier for developing.
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
Mirantis
  • Docker has made it possible for us to deploy code faster, increasing the productivity of our development teams.
  • Docker has made it possible for us to decentralize our build and release system. This means that teams can deploy on their own schedule and our dev ops team can concentrate on building better tools rather than deploying for the teams
  • Docker has allowed us to virtualize our entire development process and made it much simpler to build out new data centers. This, in turn, is significantly increasing our ROI by providing a path forward for internationalization.
Read full review
ScreenShots