Microservices and Docker go together like chocolate and peanut butter: microservice architectures provide organizations a tool to manage complexity of the development process, and application containers provide a new means to manage the dependencies and deployment of those microservices. But deploying and connecting those services together is still a challenge because it forces developers to design for operationalization. By pushing responsibility for understanding startup, shutdown, scaling, and recovery from failure into the application, we can build applications on autopilot. Of course we aren't going to rewrite everything to do this, so we need a way to build application containers that can knit together legacy and greenfield applications alike.
Containerbuddy is an open-source application written in Go to solve this problem. Its author, Tim Gross from Joyent, will present the problem Containerbuddy was designed to solve and then take a deep dive into Containerbuddy's design, discuss some of the tricky problems with implementing and testing an application driven by asynchronous side-effects, and give a tutorial on its use.
Tim is a product manager for Joyent, providers of the Triton Elastic Container Service. Tim was previously the head of DevOps at a streaming media company, where he and his scrappy team ran Docker in production to serve a few million fans their daily dose of dramas, documentaries, and gross-out horror movies. In a previous life, Tim was an architect (buildings, not software). He took the leap into programming and Operations after he discovered he could automate away almost everything boring in his life.