1. Microservices
with Docker
Timo Derstappen
@teemow

2. What are
Microservices?

3. Example Application

4. Definition!?
● Small, focussed services
● Independent Processes
● Language agnostic APIs
● Highly decoupled

5. Right tool for the job
● Not bound to a single Technology
● No one-size-fits-all approach

6. Resilience
● No monolith to fall over
● Design to fail
● Circuit Breakers to avoid cascading
failures

7. Distributed Systems
● Failures are going to happen
● Reduce Mean Time to Recover

8. Scaling
Only services that are constrained by
performance need scaling.
Elastic (on-demand) scaling of smaller
services leads to better cost control

9. Ease of Deployment
Services can be deployed independently and
faster.
Changing a monolith could have more impact
and risk so deployments are slower.

10. “Organizations which design
systems ... are constrained to
produce designs which are
copies of the communication
structures of these
organizations.”
— Melvin Conway

11. Composability
● Re-use
● Re-compose

12. Optimising for Replaceability
Small services are rewritten or removed
without worrying too much

13. Enabler
● Continuous delivery
● Infrastructure Automation
● Small autonomous teams
● Systems at scale
● 12 Factor Apps

14. Where does
Docker fit in?

15. Where does it match?
● Lightweight
● Fast
● One process per container
● Composability

16. Immutable Infrastructure
● Disposable components
● Make your state explicit
● Provision at build-time
● Configure at run-time

17. Docker Workflow
● Development
● Unit/Integration Tests
● Continuous delivery
● Production

18. Development

19. Your current setup?
● Vagrant
● rbenv
● nodeenv
● virtualenv

20. Dev Container
● Contains Build Tools
● Each for every stack

21. Aliases
# What about running oneshot containers
with the build tool inside.
$ alias npm='docker run --rm -ti -v
$(pwd):$(pwd) -w $(pwd) teemow/npm'
$ npm install

22. Fig
web:
build: .
ports:
- 8080:8080
volumes:
- .:/app
links:
- redis
redis:
image: dockerfile/redis

23. Build Chain

24. Jenkins - Docker Hub Integration

25. Production

26. Simple Container Hosting
Install docker on a host and start your
container.
Use fig to link your containers.

27. Container Environment
● Scheduler
● Service Discovery
● Monitoring
● Logging

28. We ♥ CoreOS
but there are lots of options here.
● Mesosphere
● Kubernetes
● Consul
● Project Atomic

29. There is a Meetup in Cologne
Docker Cologne - CoreOS Meetup
19:00, 14th October
Startplatz
Brandon Philips, CTO of CoreOS
Luke Marsden, CTO of Flocker

30. Sign up for the
Giant Swarm private Beta
Request Invite
http://giantswarm.io/

31. Thanks for listening!
Reach out:
Timo Derstappen
@teemow
@giantswarm