MICROSERVICEORCHESTRATION

by / Co-Founder of Timo Derstappen @teemow

Giant Swarm

DISCLAIMERWe are building a container infrastructure

on top of CoreOS.

WHY MICROSERVICES?A simpl(e|ified) story!

Once upon the time there was a small web app.

Every day new features were added and the users loved it.

One day it became hard to add new features,maintain, test and scale it.

Because of that popular features were put into separateservices with their own databases.

Because of that the deployment and server provisioningwas automated.

Until finally more popular features could be added easily

THIS ALSO HELPSWITH...

Two Pizza Teams

Deploy independently

Throw-away services

BUT MICROSERVICESARE NOT FREE LUNCH!

In theory they are like nano structures

In practice they are Death Stars

Complexity is not gone

Complexity moves to the infrastructure

But now we have small immutable artifacts.

With clear separation between build- and runtime

All things will be good

But what are we going to use in production?

SOME USEFULCONCEPTS

LINK CONTAINERS ACROSS HOSTSDocker can link two containers on a single host. Let's

simulate that across hosts.

THREE-TIER APPLICATION

SIDEKICK

AMBASSADOR

CONTAINER INJECTIONConfigure your containers with other containers. Similar to

dependency injection

Single ResponsibilityIndependent from runtime environment

CONTAINER CHAIN

CONTAINER CHAIN

CONTAINER CHAIN

CONTAINER CHAIN

CONTAINER CHAIN

DISTRIBUTED CONTAINER CHAIN

DISTRIBUTED CONTAINER CHAIN

DISTRIBUTED CONTAINER CHAIN

DISTRIBUTED CONTAINER CHAIN

SUPERVISION

SUPERVISION

DEMO

THANKS FOR LISTENING!Timo Derstappen

@teemow

Co-Founder of Giant Swarm