Both Swarm and Kubernetes rely on the concept of services as a key orchestration element, and a durable endpoint for the collection of like containers. By like containers, we mean they share the exact same image for all container instances. For example, if a container running in your cluster needs to call an API running in another container, the caller can use the API container's service name, rather than using a container IP. This is really important because, in an orchestrated environment, containers can be replaced by the orchestrator at any time, and the resulting container will have a new IP. Therefore, using the service name assures the caller a connection to a running version of the container, which they need. ...
Docker Swarm services
Get Mastering Docker Enterprise now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.