Containers as a Service with Docker

Editor's Notes

• #11: The Docker mission is enable organizations to build, ship and run distributed applications anywhere.
• #19: Leading to the Docker Journey – What we have learned from the millions of developers that have already traveled this journey is that The promise of agility (speed and flexibility) drew them to Docker, with how quickly they could setup their development environments to the realization that these new containers were now portable to any environment like never before. These two things are what made Docker hugely successful in the developer community with the CI use case. But CI only realizes half of the potential value of Docker because the app pipeline just switches back to a “waterfall” or “over the wall” at deployment. In order for the much loved developer platform to gain widespread adoption in an organization, the right management construct was required. To provide this much needed control, platforms (PaaS) and bundled solutions (i.e. Tectonic) emerged in an attempt to complete the journey but their approach ends up sacrificing portability and agility for the user. Thousands of Docker users chose to not adopt those solutions and instead built it themselves with glue code and bash scripts because they didn’t want to forego the agility and portability that drew them to Docker in the first place. Just a simple search on Github for ‘Docker’ will show the ecosystem of tools written by users and shared with the community So, where do we go from here?
• #20: To do that, we can accelerate our path by learning from those who have traveled this path before and avoid common pitfalls when investigating solutions. An environment that is too locked down becomes a hassle for developers and adoption will suffer. Shadow IT behavior will emerge and developers will start creating new tools and processes to be able to use the languages they need and complete their work. EXAMPLE: BBC News had a locked down CI environment that did not include the tooling needed by many of the developers so the team created a side process to use the languages they needed. That not only went outside the official systems but then added a few days to each CI job. 2) Many of the existing solutions on the market are either too opinionated of a PaaS or are cobbled together solutions with a number of different products. These solutions can be difficult to deploy and manage over time. More specifically, many of them support the Docker format or take the Docker code and customize it for their solution environment. This can break not only the developer experience but also the ops side of the experience because they only supporting parts of the Docker API – so the user will not experience the desired behavior in all situations. This also breaks the ecosystem because the hundreds of partners building to the API may have compatibility issues against these solutions. 3) Portability is a default requirement for distributed applications. As the content creator, you must retain control of where that app lives and your ability to move it from environment to environment, to a different team and to different infrastructure providers. Other pitfalls… Developers will run entire application lifecycle outside of infra ops (shadow IT) Infrastructure-centric “container solutions” break developer experience Organizational finger-pointing is compounded because of stifled productivity Legacy applications get overlooked Gilt also shares the example where emphasizing control lead to a “cycle of suck” where they were taking longer to ship and with less innovation
• #30: Local development environments Self service app images Build, Test, Deploy applications Define app behavior and infra needs Registry services for image storage, management and distribution IT Ops maintains library of secure base content Manage role based access to repos/images Management consoles Provision, manage infrastructure resources Monitor, manage, scale infrastructure and applications
• #32: Docker is the only solution to give you agility, control and portability for all your distributed apps. The right choice in helping transform your business into an agile business. The platform is the only commercially supported Docker solution available on the market today. Other vendors who state they support Docker is not actually providing technical support and maintenance into the Docker product code. Docker is the only commercial yet open platform that gives you the operational flexibility you need. And unlike other solutions, Docker is… Language agnostic: C, Java, Phython, PHP, Go…. Infrastructure agnostic: on-prem, cloud, virtual, bare metal All stages: from dev to test to release engineering to production Any OS: Linux, Windows, Solaris Docker enables agile distributed applications in production to create agile companies
• #33: So these
• #34: This leading phahas a hybrid cloud environment and would like to have a portal to completely abstract away the infrastructure details from their app teams. This way in the portal they request compute resources. Depending on if the app is regulated or not, the actual provisioning and deployment will happen to either an AWS VPC or their private datacenter. In addition to the portal, J&J would like to add a central IT managed marketplace to get app templates and images to help the teams get started. Once provisioned, the actual deployment and ongoing management is de-centralized and owned by the application teams. Use Cases - Developer self service - Hybrid cloud portability - Multi cloud environment Why Docker? App portability is a MUST. Over time they want the option to move the DC apps to cthe cloud as regulations change. Additionally they have already added Azure to their environment and would like to be able to move apps to the new clouds.
• #35: ADP operates in a more traditional centralized IT model where IT manages and operates the application and environment ongoing. ADP looked at Docker as they began their transition to DevOps. They were interested in gaining more efficiencies and re-use of code by moving to a shared services model instead of monoliths with a lot of repeat services. ADP has OpenStack for their private cloud and AWS for their public cloud. As part of the transition, ADP would will setup a central marketplace where the shared services apps are available for the app teams. In the ADP example both the environment and ongoing management remains centralized. Use Cases - Transition to Micro services - Enable Dev Ops - CI/CD Why Docker? Need app portability so they can choose to move across AWS / Openstack