github/container.training
1
0
Fork 0
mirror of https://github.com/jpetazzo/container.training.git synced 2026-07-18 20:39:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify service discovery

Browse Source
This commit is contained in:
Jerome Petazzoni
2018-02-27 14:45:08 -06:00
parent 893f05e401
commit 5bc4e95515
1 changed files with 25 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
slides/common/sampleapp.md
View File

@@ -39,21 +39,15 @@ class: extra-details
---
## Links, naming, and service discovery
## Service discovery in container-land
- Containers can have network aliases (resolvable through DNS)
- We do not hard-code IP addresses in the code
- Compose file version 2+ makes each container reachable through its service name
- We do not hard-code FQDN in the code, either
- Compose file version 1 did require "links" sections
- We just connect to a service name, and container-magic does the rest
- Our code can connect to services using their short name
(instead of e.g. IP address or FQDN)
- Network aliases are automatically namespaced
(i.e. you can have multiple apps declaring and using a service named `database`)
(And by container-magic, we mean "a crafty, dynamic, embedded DNS server")
---
@@ -80,6 +74,26 @@ https://github.com/jpetazzo/container.training/blob/8279a3bce9398f7c1a53bdd95187
---
class: extra-details
## Links, naming, and service discovery
- Containers can have network aliases (resolvable through DNS)
- Compose file version 2+ makes each container reachable through its service name
- Compose file version 1 did require "links" sections
- Network aliases are automatically namespaced
- you can have multiple apps declaring and using a service named `database`
- containers in the blue app will resolve `database` to the IP of the blue database
- containers in the green app will resolve `database` to the IP of the green database
---
## What's this application?
--