Creating Distributed apps with Weave and the Docker platform Ilya Dmitrichenko 

Docker is great! • Highly portable delivery framework • Fuelling CI/CD/DevOps with • tight and transparent dependency packaging • good isolation, without virtualisation overhead • easy to setup, manage and automate 

Ok, I want Docker! • I surely want to use Docker as a foundation for building my microservices architecture, it looks just right. • I also see many other great tools that are related, e.g.: • Kubernetes/Mesos/Marathon/Swarm • Terraform/Brooklyn/fleet/Machine • etcd/Consul/Zookeeper • OK, may be I should start with what Docker Inc offers 

Docker platform • Docker engine itself • Swarm - native clustering • Machine - VM provision • Compose (aka Fig) 

Compose • Front-end of the Docker platform • A great tool that all developers love • Very simple and easy to use • Inherently single-host (just like Docker itself) 

Compose + Swarm • Go multi-host! • Well, sort of… • Container links are still single-host only • No out-of-the-box networking 

Compose + Swarm + Weave • Go multi-host for the win! • No links • No ambassadors • No port remapping 

Example web: build: . command: python app.py ports: - "5000" volumes: - .:/code hostname: hello.weave.local environment: - "affinity:container!=app_web_*" redis: image: redis hostname: redis.weave.local 

Weave & Docker • Simple, secure and reliable • Overlay network with built-in automatic DNS • Application-oriented — lean and flexible • Scales as you grow without any code changes • Make Docker platform much easier to use 

–Adrian Cockroft (@adrianco) “Weave Net makes it as easy as possible for developers to create a network of Docker containers. I’m excited to see the addition of Weave Scope to visualise that network.” 

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

Demo! GOTO: weave.works/guides/weave-and-docker-platform 

Thanks! Questions? • weave.works/ • @weaveworks In production at