Running your own DBaaS based on your preferred DBs, Kubernetes operators and containerized storage

Click for: original source

Posted by Evan Powell this is excellent guide for those who want to get advice about running their own Redis or Cassandra or MongoDB in Kubernetes.

Many enterprises such as financial service and health care providers or those that are concerned about AWS as a competitor choose to run their own Kubernetes on their own environments in part due to concerns about data being viewed by the cloud provider or by some external attacker.

There is a huge number of DB solutions. There are at least eight main types: key value stores, column stores, document stores, graph databases, row stores, in memory database, “synthetic” – able to retain consistency while scaling horizontally, time series databases…

The article then dives into:

  • Composing a stack that better serves the DB
  • Integrating your disparate data sources more easily
  • DevOps autonomy
  • Problems with building and running stateful workloads

And much more in the article. It outlines some of the things to think about when running your own DBaaS. Well worth the read!

[Read More]

Tags kubernetes programming devops