Amazon EC2 Container Service聽vs聽Docker Swarm

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Amazon EC2 Container Service
Amazon EC2 Container Service

3.3K
2K
+ 1
324
Docker Swarm
Docker Swarm

418
401
+ 1
207
Add tool

Amazon EC2 Container Service vs Docker Swarm: What are the differences?

Developers describe Amazon EC2 Container Service as "Container management service that supports Docker containers". Amazon EC2 Container Service lets you launch and stop container-enabled applications with simple API calls, allows you to query the state of your cluster from a centralized service, and gives you access to many familiar Amazon EC2 features like security groups, EBS volumes and IAM roles. On the other hand, Docker Swarm is detailed as "Native clustering for Docker. Turn a pool of Docker hosts into a single, virtual host". Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.

Amazon EC2 Container Service can be classified as a tool in the "Containers as a Service" category, while Docker Swarm is grouped under "Container Tools".

"Backed by amazon" is the top reason why over 97 developers like Amazon EC2 Container Service, while over 43 developers mention "Docker friendly" as the leading cause for choosing Docker Swarm.

Docker Swarm is an open source tool with 5.61K GitHub stars and 1.11K GitHub forks. Here's a link to Docker Swarm's open source repository on GitHub.

According to the StackShare community, Amazon EC2 Container Service has a broader approval, being mentioned in 784 company stacks & 374 developers stacks; compared to Docker Swarm, which is listed in 80 company stacks and 38 developer stacks.

- No public GitHub repository available -

What is Amazon EC2 Container Service?

Amazon EC2 Container Service lets you launch and stop container-enabled applications with simple API calls, allows you to query the state of your cluster from a centralized service, and gives you access to many familiar Amazon EC2 features like security groups, EBS volumes and IAM roles.

What is Docker Swarm?

Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Amazon EC2 Container Service?
Why do developers choose Docker Swarm?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use Amazon EC2 Container Service?
    What companies use Docker Swarm?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Amazon EC2 Container Service?
    What tools integrate with Docker Swarm?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Amazon EC2 Container Service and Docker Swarm?
    Kubernetes
    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
    Google Kubernetes Engine
    Container Engine takes care of provisioning and maintaining the underlying virtual machine cluster, scaling your application, and operational logistics like logging, monitoring, and health management.
    Amazon EKS
    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.
    AWS Fargate
    AWS Fargate is a technology for Amazon ECS and EKS* that allows you to run containers without having to manage servers or clusters. With AWS Fargate, you no longer have to provision, configure, and scale clusters of virtual machines to run containers.
    Docker for 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.
    See all alternatives
    Decisions about Amazon EC2 Container Service and Docker Swarm
    Yshay Yaacobi
    Yshay Yaacobi
    Software Engineer | 27 upvotes 211K views
    atSolutoSoluto
    Docker Swarm
    Docker Swarm
    Kubernetes
    Kubernetes
    Visual Studio Code
    Visual Studio Code
    Go
    Go
    TypeScript
    TypeScript
    JavaScript
    JavaScript
    C#
    C#
    F#
    F#
    .NET
    .NET

    Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

    Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

    After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

    See more
    Russel Werner
    Russel Werner
    Lead Engineer at StackShare | 0 upvotes 3.8K views
    atStackShareStackShare
    Amazon EC2 Container Service
    Amazon EC2 Container Service
    CircleCI
    CircleCI
    Helm
    Helm
    Slack
    Slack
    Google Kubernetes Engine
    Google Kubernetes Engine
    Amazon EKS
    Amazon EKS
    Kubernetes
    Kubernetes
    Heroku
    Heroku

    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.

    See more
    Interest over time
    Reviews of Amazon EC2 Container Service and Docker Swarm
    No reviews found
    How developers use Amazon EC2 Container Service and Docker Swarm
    Avatar of CloudRepo
    CloudRepo uses Amazon EC2 Container ServiceAmazon EC2 Container Service

    We use the container service so that we can deploy our application services with Dockerfiles, so that we can test locally and deploy to AWS simply.

    Additionally, the ability to scale containers and have them automatically restart in case of failure is very helpful to our operations.

    Avatar of Adminout
    Adminout uses Amazon EC2 Container ServiceAmazon EC2 Container Service

    We use the EC2 registry for secure private container registration. When used in combination with I AM roles we can control customer access to repos on and individual basis.

    Avatar of SocialCops
    SocialCops uses Amazon EC2 Container ServiceAmazon EC2 Container Service

    Amazon EC2 is our primary application hosting solution. Most applications are not exposed on the internet and use a virtually private cloud to interact with each other.

    Avatar of Brandon Adams
    Brandon Adams uses Amazon EC2 Container ServiceAmazon EC2 Container Service

    With a little forethought, ECS can handle a good portion of my development stack as though it were production. 12 Factor configuration makes this a breeze.

    Avatar of Thomas Zickell
    Thomas Zickell uses Amazon EC2 Container ServiceAmazon EC2 Container Service

    I don't like AWS BUT Pagely's VPS-3 makes it work. I still use FireHost for most things

    How much does Amazon EC2 Container Service cost?
    How much does Docker Swarm cost?
    Pricing unavailable