Docker network internal portable#

This is how the Docker вЂњnetworkвЂќ abstraction ( CNM) was born. This heavily depends on what abstractions we expose to the application developer and more importantly what abstractions we do not expose to the application developer. Similarly, when the application developer defines their application stack as a set of distributed applications, it should work just the same whatever infrastructure it runs on. A Docker container created using an image works the same regardless of where it runs as long as the same image is used.

Docker network internal portable#

The other guiding principle is to extend the same portable experience of Docker containers to networks. We want developers to be able to bind their microservices into a single distributed application using a few simple вЂњnetwork creationвЂќ and вЂњnetwork connectionвЂќ commands. We should eliminate the connectivity/discoverability headaches and portability concerns that hinders an application developer from converting a monolithic application to a set of microservices. Our belief is that by hiding the gory details of how network connectivity and service discovery is achieved behind a simple API and UI, we enable the application developers to develop their distributed application stack more freely. One of the guiding principles in the Docker Networking design is to relieve the application developer from worrying about the network plumbing details. The application developerвЂ™s concern generally ends at the Layer4 service layer that their applications are bound to. In fact they donвЂ™t even want to know what IP addresses their applications are bound to. Users: Application developersДЄs much as application developers want their applications to communicate with each other, most donвЂ™t want to understand or get involved in the details of how exactly that is achieved. Anyone in the ecosystem claiming to support or include Docker must adhere to maintaining user experience and portability otherwise it simply isnвЂ™t Docker. With that in mind, it is our belief that all APIs and UI must be exposed to end users and anything else would compromise on the core values.

That also means supporting ecosystem partners that support the same architecture goals of user experience AND seamless application portability. We wanted to give the right kind of tools to both these kinds of users so that they are empowered to easily accomplish their goals and you can read about some of the experiences from the Docker community like and primary focus is on the user, whether they are from the application team or IT operations.

The network IT team who configures and manages the infrastructure.

The application developer who wants to create and deploy a distributed application stack on the Docker platform.

When it comes to networking, there are two kinds of users:

Networking follows the same philosophy and we iterated several times to find the right abstractions for the user.

New features are always continuously refined and iterated upon so that the end product delivers the best possible user experience. Users FirstДockerвЂ™s philosophy is to build tools that have a great user experience and seamless application portability across infrastructure. As the networking capabilitiesВ evolving with every release, we wanted to spend some time explaining the guiding principles behind the design. From the experimental networking in Docker 1.7 to the initial release in Docker 1.9, the reception from the community has been fantastic! First of all we want to thank you for all the discussions, evaluations, PRs and filed issues.