Deliver Docker containers continuously with ECS
Philipp Garbe, Docker Captain and Lead Platform Engineer at Scout24, gives us an overview of ECS and all the other services you will need in order to run your containers in production.
With Docker, it became easy to start applications locally without installing any dependencies. Even running a local cluster is not a big thing anymore. AWS on the other side offers with ECS a managed container service that states to schedule containers based on resource needs, isolation policies, and availability requirements. Sounds good, but is it really that easy?
In this talk, you’ll get an overview of ECS and all other services that are needed to run your containers in production. Philipp Garbe shows us how an ECS cluster and your containerized applications can automatically be deployed and scaled. He also shares his experiences and explains which features are still missing.
SEE ALSO: A practical guide to Docker and µService: What you need to know to avoid suffering
QLIUWGEQOUZEW
Make sure you check out our Docker Captains interview series
- “Docker doesn’t want to be replaced as the container runtime of choice”
- Docker vs. VM: What’s the difference?
- Solving Docker confusions one by one — Docker Captains share their tricks
- “It is crucial for Docker to be the industry-wide accepted standard”
- Docker Captains speak bluntly: “Containerd is basically the real engine behind Docker”
- “Making containers usable with nice tooling was the only thing missing — Docker provided that”
- “Data persistence is the most misunderstood element by Docker users”
- “I feel like Docker Swarm needs a bit more work to really be usable in production out of the box”
- “Docker has created a new tool-set which has now become the standard for DevOps.”
- “Although containers existed long before Docker, it brought a revolution that was already happening to the masses”
