Amazon EKS vs Docker for AWS: What are the differences?
Developers describe Amazon EKS as "Highly available and scalable Kubernetes service". Amazon Elastic Container Service for Kubernetes (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on AWS without needing to install and operate your own Kubernetes clusters. On the other hand, Docker for AWS is detailed as "Install a Swarm of Docker Engines secured end to end with TLS by default on AWS". An integrated, easy-to-deploy environment for building, assembling, and shipping applications on AWS, Docker for AWS is a native AWS application optimized to take optimal advantage of the underlying AWS IaaS services while giving you a modern Docker platform that you can use to deploy portable apps.
Amazon EKS and Docker for AWS belong to "Containers as a Service" category of the tech stack.
Moogsoft, Condé Nast, and Cuemby are some of the popular companies that use Amazon EKS, whereas Docker for AWS is used by Trussle, Opsani, and Bontix. Amazon EKS has a broader approval, being mentioned in 27 company stacks & 8 developers stacks; compared to Docker for AWS, which is listed in 13 company stacks and 8 developer stacks.
What is Amazon EKS?
What is Docker for AWS?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Amazon EKS?
Why do developers choose Docker for AWS?
What are the cons of using Amazon EKS?
What are the cons of using Docker for AWS?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We began our hosting journey, as many do, on Heroku because they make it easy to deploy your application and automate some of the routine tasks associated with deployments, etc. However, as our team grew and our product matured, our needs have outgrown Heroku. I will dive into the history and reasons for this in a future blog post.
We decided to migrate our infrastructure to Kubernetes running on Amazon EKS. Although Google Kubernetes Engine has a slightly more mature Kubernetes offering and is more user-friendly; we decided to go with EKS because we already using other AWS services (including a previous migration from Heroku Postgres to AWS RDS). We are still in the process of moving our main website workloads to EKS, however we have successfully migrate all our staging and testing PR apps to run in a staging cluster. We developed a Slack chatops application (also running in the cluster) which automates all the common tasks of spinning up and managing a production-like cluster for a pull request. This allows our engineering team to iterate quickly and safely test code in a full production environment. Helm plays a central role when deploying our staging apps into the cluster. We use CircleCI to build docker containers for each PR push, which are then published to Amazon EC2 Container Service (ECR). An
upgrade-operator process watches the ECR repository for new containers and then uses Helm to rollout updates to the staging environments. All this happens automatically and makes it really easy for developers to get code onto servers quickly. The immutable and isolated nature of our staging environments means that we can do anything we want in that environment and quickly re-create or restore the environment to start over.
The next step in our journey is to migrate our production workloads to an EKS cluster and build out the CD workflows to get our containers promoted to that cluster after our QA testing is complete in our staging environments.