Slide 1

Slide 1 text

Deploying Microservices with Weave and Mesos Ilya Dmitrichenko

Slide 2

Slide 2 text

About Weaveworks: Connect, Observe & Control

Slide 3

Slide 3 text

Simple. Portable. Transparent. • The most productive way for developers to connect, observe and control Docker containers • Automatically works with every application • No extra code • Simple, scalable, fast

Slide 4

Slide 4 text

– Adrian Cockroft, @adrianco “Weave Net makes it as easy as possible for developers to create a network of Docker containers.”

Slide 5

Slide 5 text

Docker for Microservice • A standard unit of deployment and isolation • One can build DIY CI/CD system around it easily • Or use an orchestration platform, e.g. Swarm, Kubernetes or Mesos • Weave makes any of these use-case even easier

Slide 6

Slide 6 text

Connect: Weave Net • Create virtual networks around your apps • Push as much as you can down the stack • Do not inject any special logic or libraries • Use default ports for HTTP or databases • Use tools your already know • Import legacy services • Simple security for hybrid-cloud or multi-tenancy

Slide 7

Slide 7 text

Control: Weave Run • Orchestrator-independent lean service discover and load balancing • Distributed state management without databases • Checkout Bryan’s talk: • http://bit.ly/weave-london-container-camp-2015

Slide 8

Slide 8 text

Observe: Scope • Scope automatically generates a map of your containers, enabling you to intuitively understand, monitor, and control your applications. • weave.works/scope

Slide 9

Slide 9 text

Weave and Mesos • Provides LB and SD via DNS, literally zero-config and no KV store require • Simple to follow, Vagrant-based demo • Removes insecure and cumbersome host port mapping that vanilla Mesos setup has • Use default ports and hostnames • no messing about with HAProxy configs • no need to integrating a client library for a KV store

Slide 10

Slide 10 text

Demo time! Follow the guide at home http://bit.ly/weave-mesos-marathon

Slide 11

Slide 11 text

Questions? @errordeveloper @weaveworks