In this article on Container Journal, I make the case for why a database needs to run on Kubernetes in order to be considered truly cloud-native.
If we’re not pushing for greater maturity in cloud-native databases, we’re missing a big opportunity. To make databases the most “cloud-native” they can be, we need to embrace everything that Kubernetes has to offer. A truly cloud-native approach means adopting key elements of the Kubernetes design paradigm. A cloud-native database must be one that can run effectively on Kubernetes.
The article goes on to share the Kubernetes design principles that point the way:
- Leveraging compute, network and storage as commodity APIs
- Separating control and data planes
- Making observability easy
- Making configurations secure by default
- Preferring declarative configuration