If you are reading this blog, I hope you like sports analogies (especially baseball). In 2007, Dustin Pedroia, the infielder for the Boston Red Sox, joined the team and (along with winning a championship) was name the American League Rookie of the Year.
In 2008, Pedroia’s excellence continued and he won the AL MVP, Gold Glove and Silver Slugger awards. He has been a mainstay of the Red Sox for over a decade now. In 2013, Black Duck Software named Docker an Open Source Rookie of the Year and, like Pedroia, Docker has continued to excel and just now is hitting its prime. In fact, many have said that the adoption rate for Docker is record setting.
Stepping up to the Plate
With regards to Docker at Black Duck Software, we are really stepping up to the plate. For a while, Black Duck Software provided images on Docker Hub so that the Black Duck Hub (our Open Source management solution) could be run under Docker. Our implementation, though convenient for administrators to quickly install or update the Hub application, did not take advantage of all of the capabilities and benefits that a fully “Dockerized” application could enjoy. Well, that's changed with the Hub v3.6 release.
Black Duck Hub Available as a Fully Dockerized App
This architecture change brings significant improvements to our customers. With the new architecture, the Hub is now available to be run as a set of Docker containers for the various components in the application. Rather than using our own custom orchestration method (which we called “appMgr”), the Hub will now leverage Docker-based mechanisms.
This change enables you to use other third-party orchestrations tools to manage all of the individual containers. Initially, we'll support Docker Compose with Docker Swarm (and others soon following). Over time, we'll begin phasing out the old single container Docker and appMgr implementation and providing assistance to customers who can’t use Docker and need native Linux tooling methods.
This means improvements for customers in the following areas:
- Installing and updating the Hub
- Component orchestration and stability
- Scalability and performance
The new Docker architecture was released as a public beta with v3.6 on April 6. Since then, a number of customers and prospects have taken advantage of the new architecture. Though the responses have been very positive, we are asking customers to wait until the 3.7 GA release to deploy this new architecture in production. Hub 3.7 is coming out in May ’17, so you won’t have to wait long.
Why the New Architecture?
So, if you are a Black Duck customer, why would you care about the new Docker architecture? Well, with Dustin Pedroia you have an excellent hitter who plays legitimate Gold Glove caliber defense. With Docker (and containers in general), you also have multiple benefits. If you are an IT administrator responsible for managing the Hub application at your company, you'll appreciate the additional deployment flexibility that the new architecture enables.
This includes (among others) the ease to deploy Hub containers in the cloud, updating containers during software upgrades, managing multiple Hub environments, and scaling or distributing Hub containers to optimize the workload in your organization. If you are a person more concerned with effectively managing open source software in your company, know that Docker will help Black Duck with our software delivery pipeline, allowing us to deliver more features over time, and make it easier for you to deploy those features. It is truly a win-win, which will make life easier for our customers (big and small companies) and us.
So, on the field of Docker, Black Duck is yelling “Play Ball!" And due to all the customer applause, we are pretty sure we just hit a home run.