Give Nomad second chance

I was researching how to set up a Nomad cluster when I clicked on the top Google result. Imagine my surprise when I realized I was reading my own blog post from 2023.

That moment of accidental self-discovery made me think - maybe it's time to give Nomad another shot. Last time I tried it, I ran into enough friction to shelve the project. But if my old post was ranking well enough to appear in my own searches, perhaps the ecosystem had matured.

What Changed Since 2023

Last time I tried Nomad, I spent more time fighting the setup than actually using it. Coming from Docker Compose, the jump felt unnecessarily complex.

This time around, things clicked faster. Maybe I got better at reading HashiCorp docs, or maybe they got better at writing them. Either way, I had a working cluster in an afternoon instead of a weekend.

The real difference was finding actual production examples instead of toy configurations. Turns out people are running real workloads on Nomad now, not just demos.

The Terraform Module Discovery

While checking if anything in my setup had become obsolete, I stumbled across someone who had transformed my Terraform code into a proper module. No attribution, but honestly? I wasn't bothered. If anything, it validated that the approach was sound enough for someone else to productize.

Open source works best when people build on each other's work. The fact that my hacked-together configuration became someone's polished module means I helped solve a real problem. That's worth more than a credit line.

Technical Details Coming

This time around, I'm documenting the full journey - from bare metal to running services. The next posts will cover the actual implementation details, including what worked, what didn't, and how the Nomad ecosystem has evolved.

Stay tuned for the technical deep dive.