3 ms·
I could throw the "you'll know it when you see it" but I'll try not to! 1. You have a large amount of underused hardware/VM 's you want to cluster. 2. You have
by tnolet 8y ago
I could throw the "you'll know it when you see it" but I'll try not to!
1. You have a large amount of underused hardware/VM 's you want to cluster.
2. You have an eloborate microservices system with a dynamic service discovery mechanism.
3. You have the above over many regions / teams.
4. All your services are mostly stateless.
5. Your team of rockstar ops engineers are building their own crappy version of Kubernetes just to deal with the engineering challenges your business faces.
- cogman10 8y agoFunnily, my current employer is just that. We predate K8s, so it can be forgiven somewhat. Transitioning, though, is just awful. We have every reason to transition, yet getting the system setup, running, and working with the current infrastructure is a daunting task. You don't need K8s, until you do, at which point switching can be a nightmare scenario.
- swyx 8y agothanks, i'm pretty far from that world then, haha. appreciate the list of concerns, i hope to someday worry about these things.