October 8, 2014
Move Fast, Don’t Break the API
Amber spends most of her time building things at Stripe and figuring out how to scale their product engineering organization.
DockerCon is just around the corner, and as you may have heard, “Containers are the Future” ;). With that in mind, let’s take a look at some of the biggest questions surrounding Docker in the present.
In a recent presentation to Heavybit member companies, CircleCI CEO Paul Biggar presented some Docker Infrastructure questions to the community. His two biggest questions were:
Since then, we’ve had a number of conversations around the Heavybit clubhouse about how our members are managing these aspects of their Docker usage.
Stephen Nguyen offered Iron.io’s approaches:
In a recent Heavybit Speaker Series event, Docker’s own Jérôme Petazzoni discussed what he believes are ‘Best Practices in Dev to Production Parity for Containers’.
Said Petazzoni, “The idea is to do one thing, do it well, just like the Unix philosophy. We have one container for the component itself, for our application code. Then we have a separate container for logging. Another for monitoring. Another for backups if we have some data behind this container. Another for debugging when we need to, and so on, and so on.”
Despite the widespread use of containers and Docker in particular, the orchestration and management of in production containers is still an area of discovery and growth. Companies like Iron.io and CircleCI continue to test the boundaries of containers and continue to build new processes over time.