User Avatar

Cora Iberkleid 🚢

🌊Kubernetes

4y ago

Developer Advocate at Tanzu by Broadcom focused on Kubernetes and Spring related technologies.

My first act of heroism as a student computer lab assistant in the late 90s was unjamming a printer so that a frenzied PhD candidate could hand in their thesis. My second was replacing the magenta ink cartridge. I'd hoped to learn about computers; instead, I got suckered into printer maintenance.

Print jobs rely on the printer to provide everything necessary. Sometimes they require highly curated machines with fancy paper and staples. It takes significant effort to make sure each printer is always up to the task, and any setback can delay all jobs stubbornly lining up at the same destination. No wonder there were never more than a handful of printers in each lab.

If only we could package a tiny printer with sufficient ink and paper (and staples!) into each print job.

Then I would just need to plug the job into an electrical outlet. I could even copy the package and get the job done in half the time! No more babysitting printers.

We've been managing applications and environments in the same cumbersome way as print jobs and printers for decades. A successful deployment is the tenuous result of careful coordination between dev and ops to make sure the target environment has the proper runtime, libraries, configuration and resources needed for a particular application. It's a thankless job that must be repeated every time there is a change.

If only we could package a lightweight runtime and other necessary dependencies along with the application. Then we would just need to drop that package (or many copies of it) into an unfussy virtual machine. And by unfussy, I mean liberating.

Good news: containerization is the act of packaging all dependencies with an application using a standard format.

Containerization breaks the bondage between dev and ops and empowers each to reach a higher level of self-determination.

It sounds dramatic, but the impact of containerization has been exactly that. Development teams can take ownership of every aspect of their application and provide greater assurance that things will work as intended. Operations can use a simple common blueprint for all virtual machines and scale up and down as needed. By agreeing on a few simple packaging standards, dev and ops can clearly define the terms of interoperability such as exposing input ports and capturing log output.

Containerization is the gateway to growth.

With containerization, we can take a step back and manage our applications and environments in cleaner, more streamlined ways that enable much greater repeatability, resilience, and scale.

Can your print job do that?