26 Feb 2016
Docker containers are self-contained, isolated environments. However, they’re often only useful if they can talk to each other.
There are many ways to connect containers. And we won’t attempt to cover them all. But in this miniseries, we will look at some common ways.
This topic seems elementary, but grasping these techniques and the underlying design concepts is important for working with Docker.
Understanding this topic will:
- Help developers and ops people explore the broad spectrum of container deployment choices
- Let developers and ops people to embark more confidently with a microservice design architecture
- Empower developers and ops people to better orchestrate more complex distributed applications
Fortunately, the large number of connection options for containers enables a broad range of approaches, giving us the flexibility to choose an architecture that suits the needs of any application.
In this post, we'll look at three of the older, more basic ways of connecting Docker containers. Using this knowledge and experience as a foundation, we'll then move on to two newer, easier, more powerful ways in the next post.