Title: The Month Docker Was King And I Was A Newbie

---

November 18, 2013. This day marks the beginning of a new era in my technical career. It was just after the Docker 0.6 release, and I found myself at a startup that had just decided to take containers for a spin. My role? Well, there wasn’t one back then—so let’s call it “explorer-in-chief.”

Docker Fever

Docker was hot. The tech community was buzzing with the idea of containerization, and we were all trying to figure out how to integrate this new technology into our existing infrastructure. At my company, we had a mix of traditional VMs and a few experimental containers. It was like a playground for us, but also a bit overwhelming.

My First Encounter

My first task with Docker was simple: get it running on the servers. I spent hours pouring over the documentation and trying to make sense of the magic behind Dockerfile syntax. It felt like a new language, one that promised to simplify our deployment processes.

One afternoon, I hit a wall. The container wasn’t starting properly, and every log entry was gibberish. Frustration started to build up as I delved deeper into the logs, cross-referencing with Docker’s own troubleshooting guides. It was like trying to find a needle in a haystack of cryptic messages.

The 12-Factor App

While debugging my container, I couldn’t help but think about the 12-factor app methodology. This concept seemed almost too good to be true—a way to build applications that could run anywhere with minimal fuss. My initial excitement was tempered by the realization that our existing monolithic apps would need a complete overhaul to fit into this new paradigm.

A Spreadsheet for Everything?

On Hacker News, there were discussions about using JavaScript and Node.js for everything from web development to backend services. I read an article about someone creating a spreadsheet with just 30 lines of JavaScript. It was mind-blowing how much one could achieve without relying on complex frameworks or libraries.

My Takeaways

By the end of November, I had learned some valuable lessons. Docker was powerful but also demanded a steep learning curve. We couldn’t simply swap out our VMs for containers and expect everything to work as before. The 12-factor app philosophy was compelling, but we needed to rethink how we structured our applications.

Reflection

As I look back, this period was a mix of excitement and frustration. Docker represented a step forward in infrastructure management, but the journey from monoliths to microservices was far from straightforward. It was a reminder that change is inevitable, and sometimes the hardest part is figuring out how to make it work.

In my next post, I’ll dive deeper into our struggles with container orchestration and how we eventually integrated Kubernetes into our stack. Stay tuned!