Every once in a while I send hand picked things I've learned. Kind of like your filter to the tech internet. No spam, I promise!
Share
You Need To Learn Docker Swarm!
Published 3 months ago • 3 min read
You Need To Learn Docker Swarm!
Ever felt like you're overcomplicating your container deployments?
You might be.
Today, we're diving into a Docker orchestrator that's likely already on your machine (run `docker service` for a second will ya?), but you're probably overlooking: Docker Swarm.
The Underdog Orchestrator
For years (for me, the past 11 years to be exact), the path has seemed to be either simple Docker Compose or the more, WAY MORE complex, Kubernetes.
Compose is great for local development but falls short when scaling, especially when you have more than one machine, and production system doesn't? Heck, I don't know of one serious home lab running one node.
I remember asking my mentor years ago about the best container deployment options.
He told me, and I quote:
"People tend to develop emotions to technology... but remember: there's no best, there's better, there's worse, sure, but the most important rule is using the right tool for the task at hand."
This stuck with me and led me to explore alternatives whenever possible, regardless of what common wisdom says. In a way, it's the tech version of "question everything".
Docker Swarm offers a sweet spot.
It's incredibly easy to use, lets you scale, load balance applications, self-heal, manage secrets, collect logs, and much more.
It's perfect for local use, home labs, and even production systems that require a few simple nodes and a straightforward deployment.
Scaling and managing containerized applications can be a headache, especially when running local home lab, or small scale production deployments.
Most people jump straight to Kubernetes, even for smaller projects.
If you pick a K8s SaaS, like AWS's, Google or Azure, you're going to not only pay for the pleasure of having a managed control plane, you'd have to hone the skills of Kubernetes which cannot, and should not be taken lightly.
Docker Swarm offers a simpler, lightweight solution for many use cases.
If you have you compose file ready, Docker Stack will cover all the requirements you have.
If you don't, I bet that with zero knowledge, you'll have your containers running in a remote cluster in a matter of a couple of hours.
I Used Heroku Open Source Alternatives So You Don't Have To This issue is brought to you by: Enjoy fast, secure and reliable web hosting with Hostinger. Use "devopstoolbox" at checkout of extra discounts on op! Start hosting with Hostinger today! I recently went down the rabbit hole of self-hosted application platforms. Just 5 weeks ago I made a video covering Coolify end 2 end.Once that got released (or maybe, because of that?) I started seeing many similar, open source, self-hostable...
SQLite Is the ULTIMATE Choice For 99% of Projects When you need to crack a nut, you grab a nutcracker, not a sledgehammer. So why, when it comes to databases, do so many of us immediately reach for a heavy, complex solution, just because we “feel” it’s right? too much? This simple question changes how you look at building software.The default solution for most developers is to spin up a dedicated database server like MySQL, Postgres, or a NoSQL option. This means dealing with separate running...
I've Been Using AWS Wrong for YEARS... For years, my approach to AWS felt like a battle. As a DevOps engineer and later and architect, building infra always involved a tedious process of carefully building templates and structure, reviewing, deploying, testing and iterating over and over. I’d either spend hours clicking through the console or writing endless infrastructure code, always feeling like I was one misconfiguration away from a headache. It turns out, I was making it much harder than...