Designing for self-orchestrating applications https://www.devopsdays.org/events/2017-minneapolis/program/tim-gross/
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
exercise00
exercise01
exercise02
exercise03
exercise04
exercise05
host
image-base
instructor
slides
student
.gitignore
README.md

README.md

Designing Self-Orchestrating Applications

Abstract

Deploying applications in containers and connecting them together is a challenge because it forces developers to design for orchestration. The container ecosystem has largely converged on abstracting orchestration away from the developer and making the infrastructure more intelligent. If instead we push the responsibility for understand startup, service discovery, scaling, and recovery from failure into the application, we can build architectures that empower application development teams to understand how the software they write works in production.

But even if we accept this premise, we can’t simply rewrite all our applications, so we need a way to build application containers that can knit together legacy and greenfield applications alike. In this hands-on workshop, we will build a microservices application. Starting from simple open source components, we’ll add tooling that turns these applications into a modern self-assembling stack.

This workshop is intended to be accessible to developers and operators who may beginners in the container ecosystem, and will focus a lot on the "why" questions around containers, schedulers, and networking in contrinzerized environments.

Exercises