Page 1
MICROSERVICEORCHESTRATION
by / Co-Founder of Timo Derstappen @teemow
Giant Swarm
Page 2
DISCLAIMERWe are building a container infrastructure
on top of CoreOS.
Page 3
WHY MICROSERVICES?A simpl(e|ified) story!
Page 4
Once upon the time there was a small web app.
Page 5
Every day new features were added and the users loved it.
Page 6
One day it became hard to add new features,maintain, test and scale it.
Page 7
Because of that popular features were put into separateservices with their own databases.
Page 8
Because of that the deployment and server provisioningwas automated.
Page 9
Until finally more popular features could be added easily
Page 10
THIS ALSO HELPSWITH...
Page 12
Deploy independently
Page 13
Throw-away services
Page 14
BUT MICROSERVICESARE NOT FREE LUNCH!
Page 15
In theory they are like nano structures
Page 16
In practice they are Death Stars
Page 17
Complexity is not gone
Page 18
Complexity moves to the infrastructure
Page 19
But now we have small immutable artifacts.
Page 20
With clear separation between build- and runtime
Page 21
All things will be good
Page 22
But what are we going to use in production?
Page 23
SOME USEFULCONCEPTS
Page 24
LINK CONTAINERS ACROSS HOSTSDocker can link two containers on a single host. Let's
simulate that across hosts.
Page 25
THREE-TIER APPLICATION
Page 28
CONTAINER INJECTIONConfigure your containers with other containers. Similar to
dependency injection
Single ResponsibilityIndependent from runtime environment
Page 34
DISTRIBUTED CONTAINER CHAIN
Page 35
DISTRIBUTED CONTAINER CHAIN
Page 36
DISTRIBUTED CONTAINER CHAIN
Page 37
DISTRIBUTED CONTAINER CHAIN
Page 41
THANKS FOR LISTENING!Timo Derstappen
@teemow
Co-Founder of Giant Swarm