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.
0 kommentar(er)
