Hey everyone, I've been diving into Docker for deployment setups, and honestly, it can be a bit overwhelming for a newbie. After some research, I think I can keep things simple without needing k3s because my use case doesn't involve heavy load but does require high availability and fault tolerance.
I've got a Docker Compose file with around 10 services, and I'm considering duplicating it on another node for failover purposes. My question is: will Docker Compose work well in a production environment for this, or should I opt for Docker Swarm instead? I'm using Apache Kafka as a central hub for communication among my services since it handles redundancy for me. I want to make sure I'm making the right choice for a resilient setup. Any insights from experienced users would be greatly appreciated!
1 Answer
Kubernetes might seem intimidating, but it's actually pretty straightforward once you get the hang of it. Given that your use case could demand more complexity down the line, I'd recommend just going with Kubernetes now. You might spend a little more time learning it upfront, but it'll save you headaches in the future compared to switching from Docker Swarm later on when your needs grow.
I see your point, but who's going to maintain the Kubernetes setup? Maintaining Docker is usually easier, especially for those not familiar with all the intricacies of Kubernetes. Plus, you're already using Docker Compose, so you're set up for an easier transition with less learning involved.