At the DockerCon conference in Seattle this week, the company announced the release of Docker Engine 1.12. With this release Docker is building the orchestration capabilities within the Docker Engine.\nWhile Docker has made it extremely easy to use containers, orchestration of containers remained a challenge. And orchestration is what brings the real benefit of containers to customers. Orchestration allows companies to deploy complex multi-container apps across machines.\n\u201cOrchestration is at the same stage today as containerization was before Docker,\u201d said Solomon Hykes, founder and CTO at Docker.\n\n[ Also on CIO.com: Containers vs. virtual machines: How to tell which is the right choice for your enterprise ]\n\nThere are many open source orchestration technologies, including Kubernetes and Docker Swarm, that help customers in orchestrating their containers. But by building the orchestration capabilities within Docker Engine, Docker is becoming a one-stop-shop for containers.\nEssentially, Docker Engine is bringing the capabilities of Docker Swarm and Docker Compose into the core of Docker. The company stressed in a blog post that \u201ccontainer orchestration would be easier to implement, more portable, secure, resilient, and faster if it was built into the platform.\u201d\nDevelopers can now simply turn on the "swarm mode" if they want orchestration capabilities. It\u2019s optional, which means customers can still use whatever orchestration tools they want.\nDocker said that Docker Engine 1.12 design is based on 4 principles:\u00a0\n\nSimple Yet Powerful \u2013 Orchestration is a central part of modern distributed applications; it\u2019s so central that we have seamlessly built it into our core Docker Engine. Our approach to orchestration follows our philosophy about containers: no setup, only a small number of simple concepts to learn, and an \u201cit just works\u201d user experience.\nResilient \u2013 Machines fail all the time. Modern systems should expect these failures to occur regularly and adapt without any application downtime that\u2019s why a zero single-point-of-failure design is a must.\nSecure \u2013 Security should be the default. \u00a0Barriers to strong security \u2014 certificate generation, having to understand PKI \u2014 should be removed. \u00a0But advanced users should still be able to control and audit every aspect of certificate signing and issuance.\nOptional Features and Backward Compatibility \u2013 With millions of users, preserving backwards compatibility is a must for Docker Engine. \u00a0All new features are optional, and you don\u2019t incur any overhead (memory, cpu) if you don\u2019t use them. Orchestration in Docker Engine aligns with our platform\u2019s batteries included but swappable approach allowing users to continue using any third-party orchestrator that is built on Docker Engine.\n\n\u201cAs the adoption curve for Docker continues to grow, developers have encountered\u00a0growing pains with orchestration at scale,\u201d Fintan Ryan, industry analyst with RedMonk, said in a press statement. \u201cWith the inclusion of secure built-in orchestration in the 1.12 release, Docker is providing developers with a simple-to-use, yet extremely powerful, orchestration tool while further investing in a consistent, easy-to-manage experience for operations."