Ugly connectivity challenges in your development and production environments. The good: Advances in container networking in the past year, including the emergence of “Micro SDNs” as the way to simplify Docker deployments The bad: Understanding live network behavior and troubleshooting The ugly: Multicast, security, robustness and resiliency at scale In this talk you will learn how to weave Dockerized microservices together without tying yourself in knots or putting your head in a noose. You’ll learn how to effectively use micro SDNs, service discovery and request routing. You'll also see how to solve the bad and the ugly connectivity challenges in your development and production environments.

1. Container Networking: The Good,
The Bad and The Ugly
Mathew
Lodge
Weaveworks

3. Container networking in last year
• Good: IP per container networks, auto-
updating DNS, self-wiring networks
• Bad: Understanding what’s actually going on
• Ugly: Robustness, multicast

4. Typical microservice scenario
4
Worker Worker Worker
API Client API Client
API proxy /
load balancer

5. The ugly: networking 1 year ago
5
Docker host 1 Docker host 2
Client
808080
Worker
4438443

6. The good: Networking today
6
Docker host 1 Docker host 2
Client
80
Worker
443
Ethernet bridge on Docker host VXLAN tunnel between hosts Ethernet bridge on Docker host

7. The good: DNS service discovery
7
DNS entries
10.0.0.1 www
10.0.0.2 www
10.1.0.1 svc x
10.1.0.2 svc x
10.1.0.3 svc x
10.2.0.1 svc y
10.2.0.2 svc y
www www
x x x
y y
www www
LB
Service X Service X
LB
Service Y
Service X
Service Y
Container network DNS auto-updated
with container names
App view

8. The bad: visibility

9. Good: Docker app visualization…
9

10. Good: …while retaining CLI access

11. Ugly: Single point of failure
11
Consul 1 Consul 2 Consul 3
Host Host Host Host Host

12. Good: No single point of failure
12
Host Host Host Host Host
Weave Net: router container per host with eventually consistent shared cache

13. Thank you!