I'm currently exploring blue-green deployments for microservices at my workplace, but we face a challenge: our services are tightly coupled. This means that deploying a new version of one service often requires updating several others to ensure proper communication between versions. To implement blue-green deployments, I'd need to set up a completely new environment for the green version, which will involve considerable complexity. I've come across some tools like `argo rollouts`, but they don't seem optimal for our whole ecosystem. I'm hoping to hear about any effective strategies or tools people have used in similar situations.
1 Answer
If your services are that tightly coupled, it might be better to reconsider your architecture. Maybe instead of individual pods, you could use one pod with multiple containers that communicate internally. This could help reduce complexity as you implement blue-green deployments.
That's a good point! It sounds like addressing the architecture could potentially streamline the deployment process. It's just frustrating when the team is used to shipping in batches without worrying about compatibility. It feels like a battle to change that mindset.