Container orchestration is the use of declarative configuration and imperative commands to deploy, provision, and execute containerized workloads. It automates the distribution of preprovisioned container images, injection of configuration, scheduling onto machines, life-cycle-management, and monitoring of applications, microservices, and jobs in the cloud. The orchestration space is fast moving and full of competing products, platforms, and frameworks. How do you choose the right one for your requirements?
Karl Isenberg explores the features of several container orchestrators, breaking down the feature sets and characteristics into categories, and scoring multiple solutions—including Kubernetes, Marathon, and Docker Swarm—against each other, to explain what functionality to look for in a container orchestrator, which products are good at which feature sets, and how you can apply this methodology in your research of other container orchestrators.
Karl Isenberg is a distributed systems architect at Mesosphere working on DC/OS (the Datacenter Operating System). Prior to Mesosphere, Karl worked on CloudFoundry and BOSH at Pivotal. Karl’s current side projects include Probe (a service-ready check), Inject (a Golang dependency injection library), and Mesos Compose Docker-in-Docker. Karl is, as of this writing, the only person to have been a committer on CloudFoundry, Kubernetes, and DC/OS, so he is uniquely qualified to address the container platform market, cloud-native frameworks, lifecycle management strategies, and deployment tools in general. Karl’s publications include Obfuscation, an irregularly updated tech blog, and a more active stream of technology-related tweets.
©2016, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com