Amazon EC2 Auto Scaling vs. Mirantis Kubernetes Engine

If you need to establish a system right away, in the past it took weeks or months to request a quote from the vendor and receive the equipment. Now, with Amazon EC2 in less than tens of minutes or hours, you can create a test environment and test it without any inconvenience.

[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.

Incentivized

• Dynamic scaling can be configured to respond to a wide variety of metrics and alerts
• Predictive scaling allows one to get ahead of high traffic events rather than simply reacting to them
• Health checks are configurable based on the needs of your application and architecture

Incentivized

• 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.

Incentivized

• Enable cross region auto-scaling. It currently limited to a single region.
• Support custom health check scripts, deeper integration with application-level metrics. At present, health checks are basic.
• Adding cost-aware scaling scripts that factor in instance pricing and recommend optimal configurations based on budget constraints.

Incentivized

• 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.

Incentivized

Usability is good since we already know how AWS works. For those that are new it might be a little bit confusing at the beginning but they are improving it at a fast pace. Even though AWS keeps changing the user interface constantly, it is still powerful, understandable and easy to use. For technical people, they still offer the CLI.

Incentivized

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.

Incentivized

The platform works as is. The help and tutorials on the help page can help you to setup the entire platform without problems, and also provides help on a huge variety of problems. Amazon also provides support plans. We have the basic support plan, but Amazon offers three support tiers, and we know that it works perfect.

Incentivized

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.

Incentivized

The main reason is our total infra is created on AWS and we tend to use the natural service by AWS rather than third party tools, which has more advantages when the auto scaling interacts with other AWS services and its way easy to configure when we compare it with counter parts like Autoscale from Microsoft Azure.

Incentivized

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.

Incentivized

• We will devote more time to development than server administration, but we will require additional time if you migrate from another ecosystem.
• Fault detection and reporting are automated in the old server, and bandwidth is fixed per month, but everything is manageable automatically. We only pay for the resources we use.
• After some months, we met our return on investment (ROI).

• 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.

Incentivized