DEV Community

Discussion on: Do you run your database on Kubernetes?

View post
Collapse
 
pengtan profile image
Peng Tan •

Sql, NoSql, NewSql databases run on Kubernetes and for both production and test. And all databases are deployed in helm charts.
Reason:

  • All applications (clients) are on Kubernets.
  • It is trend, more and more developers have already worked for k8s env in community for production env for different DBs, so work on k8s are good for now and future.
  • All cloud providers can provide SQL/NoSQL solution. Most NewSQL are for K8s from day 1. So it would be easy to migrate to these cloud providers' env if customers use similar env.
  • Good for customers to manage applictions in one style. And it would be easy for customers to accept the solution if it is trend even it would bring some drawbacks, because these drawbacks will be less.
  • Need good applications arch (e.g., need cache to enhance perf and reduce latency, can read only when DB is down/upg, provide tricky solution during DB upgrade/downgrade to reduce DB downtime or friendly user experience, etc)
  • Need solution level solution to consider when one site application or DB is down or upg, traffic should be reroute, e.g., geo-red solution.
  • Many ... So need more experiented developers to maintain the DBs in k8s for customers(lifecycle for upg/downgrade, scaling, resilience cases, data backup/restore, recovery etc. Back-to-back collaboration with DB community members (or cloud providers) is essential.
Collapse
 
vijaykodam profile image
Vijay Kumar Kodam •

good points. What about the stability, high availability of the database?
How do you handle the occasional failures or node crashes or node scaling in your kubernetes? How does it affect the DB?
How do you upgrade k8s while keeping database always available?