Thank you for contacting us. We will get back to you shortly.
February 24, 2016 - by Tim Gross
Mentions of Containerbuddy in this post should be read as references to ContainerPilot.
When we started work on Containerbuddy, we were trying to solve for the problem of making applications responsible for managing service discovery. But as we used Containerbuddy in other projects, we began to realize that the pattern we'd developed for service discovery applied to other aspects of a container's lifecycle: start-up, on-going orchestration, and graceful shutdown.
This culminated in the development of the autopilot pattern, an approach to application and infrastructure design that automates the repetitive and boring operational tasks of an application, including startup, shutdown, scaling, and recovery from anticipated failure conditions for reliability, ease of use, and improved productivity.
Since the first alpha release of Containerbuddy, we've added:
Containerbuddy is a small project, but this release consists of the effort from 43 pull requests from 6 contributors, only half of whom were Joyent employees. A special thanks to Justen Walker from Jet.com, who has contributed a majority of the code in the project at this point.
Please see our Containerbuddy implementation guide for a complete walkthrough of how to build applications that self-configure for easy deployment and scaling.
To see Containerbuddy in action, take a look at these videos: