mucon2015 - conduct your microservices with mesos and marathon

CONDUCT YOUR MICROSERVICESOn the path to cloud-native applications

Sylvain Hellegouarch@lawouach

Before you had one big app


Now, you have a zillion of smaller services


Why so many of them?

The big app had hidden links and dependencies.

These Functions still exist but their relationships are now public.

➢Who becomes reponsible for those?


Be careful about projecting complexity


Going forward…

StandardizeAutomate

IsolateOrchestrate

MonitorAdapt


Helping the ops!

Sysadmins cannot be expected to support thousands of dynamic services the old fashion way

We need a tool to orchestrate all of those pieces together.


Orchestration

Microservices lifecycle and relationships conductor

Orchestration brings (some) order to the microservices chaos

➢ Docker Swarm➢ Apache Mesos/Marathon➢ Google Kubernetes➢ CoreOS Fleet➢ Cloud Foundry Diego


Mesos

Cluster resources sharing

Advertizes resources to high-level schedulers and executors

Isolates executed tasks into mesos or docker containers


Mesos (misc)

Master/slave architecture

Infrastructure neutral

Docker Swarm and Kubernetes can benefit from Mesos

MesosDNS for discovery (though you can use Consul, WeaveDNS too)

Proven: used in production at airbnb, Apple, netflix, Mesosphere…

Open Source (Apache 2.0 license)


Marathon: a Mesos framework

Schedules your microservices based on needed vs available resources (offered by Mesos)

Executes microservices and manages their lifecycle


High level HTTP REST API


Marathon: Specification


Marathon: Resources

How much do you need?

➢ Match Marathon’s agent role set at startup


How should it be deployed?

➢ Match Mesos slave attributes➢ UNIQUE, GROUP BY, CLUSTER,

LIKE, UNLIKE…

Marathon: Constraints


What is the upgrade/rollback strategy?

➢ Ensures service continuity

Marathon: Upgrade


Input for redundancy/failure scenarios

➢Ensures service availability

Marathon: Health-check


Relationships to other services

➢ Manages relationships

Marathon: Dependencies


Marathon: Application definition


Marathon: More…

Application groups supported

Deployment events feedack

Straight documentation


Marathon: ChallengesNo command line, less natural for scripting

Can Marathon cope with the speed of changes brought on Docker itself?

Not a simple debugging experience

AFAIK, docker containers are never removed automatically

Might be too generic for your use case


Marathon: Getting started?Design your system so that it copes with interruptions

Define your deployment workflows carefully: install, upgrade, rollback, failover...

Use a service discovery (weave, consul, etcd, MesosDNS)

Consider using an overlay network to decouple your network from the infrastructure (weave, VXLAN)


What’s next?

Explore but be patient!

Build familiarity to gain trust and confidence


Thank you!

Questions?

[email protected]


mucon2015 - conduct your microservices with mesos and marathon

Technology