Nevertheless, portability alone can not explain why investors are pumping hundreds of millions of dollars into a startup within three years, making only a technology that has been known for a long time better manageable. One reason is that Docker was simply available at the right time.
With mid-sized and large organizations completing the consolidation of their data center infrastructure to virtual servers, so server virtualization is business-as-usal, most organizations are in the second stage of transforming their IT processes. This goes along with the question of whether desktop virtualization or server-based computing is the logical consequence on the way to a self-service-driven earnings performance of their IT or just an intermediate step into the cloud, be it SaaS , IaaS or PaaS ,
possibly even replace the cloud? read
In any case, enterprise container technology appears to be on the horizon at a time when cloud technologies are mature and well-engineered, not just in terms of backbone infrastructure requirements (such as bandwidth availability and cost), but also in terms of service models , Thus, the way to Cloud native apps is no longer far, where containers can exploit their strengths – as long as container developers find a way to ship stateful apps into containers.
Currently, cloud native apps for containerization typically need to be rewritten, while persistent storage today allows non-cloud native apps (stateful apps) to run in containers. Persistent storage in the early days of OpenStack and other cloud systems was out of the question.
Today Docker is much more than just a platform for deploying applications based on containers. Docker sparked unprecedented momentum in the open source community, which rapidly evolved into a vast ecosystem of docker and container technology tools and solutions, including management frameworks, user interfaces, app marketplaces, and monitoring Tools. Nevertheless, Docker is not unrivaled today. This is because Docker has other weak points in addition to the described and not all areas of application have been exhausted.
One of Docker’s previous concerns about ensuring trustworthiness of containers in the context of container origin may be solved with the trusted registry technology, which has been available for over half a year, along with signed containers, integration with existing leading infrastructure Environments still raises questions.
For example, evaluation of log files, integration into monitoring, recovery concepts for emergencies ( backup / restore), integration into a configuration management database (CMDB), software lifecycle management or patching have not yet been satisfactorily resolved . After all, Docker already integrates more or less with Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform , IBM Bluemix, OpenStack Nova, Puppet, Salt, Chef, or Red Hat Ansible.
Docker and the PaaS
In addition, Docker also harmonizes with Platform-as-a-Service (PaaS) environments such as Cloud Foundry or Apprenda , as well as other container platforms such as “Red Hat Openshift Origin”. However, one must not overlook that such initiatives do not emanate from Docker. Support is provided by the manufacturers of the respective solution.
Docker is and remains an open-core company whose open core is used by other manufacturers in their software. However, the multiple link points make it clear that common standards for container formats and runtime environments are extremely important.
For example, under the umbrella of the Linux Foundation, the Open Container Initiative (OCI) was launched in 2015 , a consortium of all digital society technology leaders, including Red Hat, AWS , Google, Mesosphere, Pivotal, Cisco, IBM, Microsoft, Intel, Oracle and VMware. The aim of the initiative is to establish common standards and to catch competing developments such as “CoreOS” / “Rocket” and to keep them compatible.
Microservice architectures and cloud native development
Docker, on the other hand, has been relatively late in the orchestration of containers, which, among other things, plays an important role in the scaling of multi-container based apps and services. It was not until 2015 that Docker introduced its own solutions, such as “Machine”, “Swarm” and “Compose”, although, for example, the orchestration tool “Google Kubernetes” was already well advanced at that time. The fact that container technology can be used excellently for micro-service architectures or as the foundation for cloud-native app deployment has also been recognized by companies such as Red Hat at an early stage (see: Container Technology by Red Hat).