Setting up environments, starting processes, and monitoring processes on multiple machines is painful and error prone, even with tools like tmux. When setting up a distributed development environment, a lot of things can go wrong; for example, stale settings left from previous tests, incorrect configuration on some machines, executing the wrong command on some portion of the machines, using local file systems when you need them to be shared, or file collision on shared file systems when you need them to be separate. The are lots of opportunities for mistakes that slow down progress and sap the fun from programming.
Using Docker makes life much easier: it’s simpler and faster to build a Docker image that has the common tools needed to run and debug production-level code. With the isolation of the container, you can easily start a cluster of nodes on a single physical machine, eliminating many of the difficulties encountered in developing distributed systems.
This session is designed for developers tasked with building distributed systems. I will explore how using Docker to isolate processes in a clustered environment simplifies distributed system development and debugging processes.
John Hugg has spent his entire career working with databases and information management. In 2008, he was lured away from a Ph.D. program by Mike Stonebraker to work on what became VoltDB. As the first engineer on the product, John liaised with a team of academics at MIT, Yale, and Brown who were building H-Store, VoltDB’s research prototype. Then he helped build the world-class engineering team at VoltDB to continue development of the open source and commercial products.
©2015, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org