I've been hearing that running databases on Kubernetes is often considered a bad idea, with many experts recommending services like AWS RDS or ElastiCache instead. I'm curious about the real pros and cons of running databases in Kubernetes. Can someone shed some light on this?
2 Answers
There’s no real downside if you know what you're doing! For many businesses, using Kubernetes for databases can save costs and even improve latency. But yes, it does come down to the specific needs and capabilities of your team.
It's all about knowing your workload as well. Some databases just need to be integrated into the Kubernetes lifecycle to function effectively.
Not every organization runs their own cloud! Sometimes, using Kubernetes for databases is a preferred choice, especially if you need certain flexible configurations that managed services can't provide.
Exactly! It’s about finding the right balance between managed services and what Kubernetes can offer. We've done something similar in a large organization.
But don't you have to keep the database in Kubernetes if you go that route?
Exactly. Sometimes, there might just be a necessity to keep costs low, even if it means dealing with some potential downtime.