DockerCon, Part 1: Looking Forward to This First-Ever Docker-Centric Event
Next week, the Flux7 team is attending the first annual DockerCon, a two-day Docker-centric event that is being organized by Docker Inc. By far the most exciting part for us will be presenting our developing productivity workflow with our client Auto.com, a Chicago-based online portal that delivers information and services for finding new and used vehicles, and a subsidiary of Classified Ventures.
But as we have previously done before when attending conferences, I thought I’d share what other sessions that are going to be a thrill for us. Starting from the discussions on day one, the following are the ones that got our attention.
For the first set of sessions, my priority is the one about Docker on Cloud Foundry. Docker, in many ways, is positioning itself to be a solution that offers a PaaS with the flexibility of IaaS. AWS already includes Docker in its Beanstalk offering. Cloud Foundry, an open source cross-platform PaaS, is already showing a lot of promise. So, I am very interested in learning how Cloud Foundry is working with Docker. In addition, with its own provisioning mechanism, we can potentially use Cloud Foundry to provide an end-to-end code management pipeline from developer workflow through production deployment.
At the same time, another of the talks on the agenda includes “Thoughts on Interoperable Containers.” This seems interesting. The topic is definitely valuable, and I expect to walk away from it with insights into the future and long-term potential of containers. For now, though, I’m going to keep this session as a backup.
In the next session, I’m planning to attend a discussion led by Facebook entitled “Tupperware: Containerized Deployment at Facebook.” In a developer workflow, you have to work towards setting up an end-to-end workflow. So, I’m interested in finding out what best practices Facebook is employing for deployment.
In a similar vein, I’m also curious about eBay’s talk in regard to its CI workflow. I’m eager to see what we can learn, take away from it, and how it compares to the solution using Docker that we developed with Auto.com, which averages 1.5 million unique views per month and has achieved significant improvement in its continuous delivery process as a result of our deployment. Of course, we will then apply those learnings to future projects also using Docker to create developer workflows.
In the following session, there’s a lot of promise in learning how Docker is working in conjunction with Puppet. Already, many sophisticated users of configuration management tools are speeding up toolchain development workflows using Docker. But one of the key ingredients that Docker is providing that configuration management tools aren’t yet using is the Docker ability to “diff” containers. So, I’m interested to see what is brewing in regard to traditional configuration management tools to make use of the extra visibility being provided by Docker.
The next session that is attracting my attention is one about NetDevOps. DevOps, despite the name, is not about making the Devs and Ops teams communicate better. It is the philosophical approach to maximize information being exchanged between all parts of the business to ensure everyone is working towards a common goal of success. In this quest, I’m wondering what the speaker is going to say about widening the circle of people traditionally included in the conversations surrounding DevOps. Will he or she add networking and security engineers to the mix?
After that is Aater’s session. Our Flux7 CEO and co-founder will be discussing the developer productivity workflow we set up for Auto.com. The discussion is comprised of both what is important to make sure your developers are productive and the set up created for Auto.com.
The final session I’m going to attend for the day is the one hosted by Netflix. Netflix is already proving itself to be one of the most advanced companies in terms of implementing a developer workflow. And I’m extremely excited to see what its engineers have been able to do with Docker.
So that’s what’s got us excited about the first half of the first annual DockerCon, which starts early next week. We’ll be giving you more about the second day very soon.
In the meantime, let’s keep the conversation going. Are you attending DockerCon? If so, tell us what’s got you excited about this first-ever event. If not, share what you are hoping to learn from the outcome of our DockerCon experience.