Thanks for reading. Here I try to make 5 specific predictions that we can look back on in a year. Hopefully, along with the ways, I leave some breadcrumbs that explain my thinking that could be of interest to the broader community. Feedback is welcome and needed.
1. Kubernetes becomes the preferred solution for databases, ML and related storage and data management
The first couple of assertions may be fairly innocuous. One sign of the shift of database and ML workloads onto Kubernetes is the emergence of projects like KubeDirector and the recently announced Maestro from Mesosphere for the management of stateful workloads on Kubernetes as well as the continued growth of KubeFlow and other projects for ML on Kubernetes.
KubeDirector is an interesting project that aims to eliminate a lot of the hard-coded components of many operators — replacing these with additional metadata fields. I see a few such projects emerging. An operator for stateful workloads that we see used some in the OpenEBS community is https://kubedb.com which supports several workloads such as Elastic and MySql. And just about every database has an operator or two from the project or related projects, with CrunchyDB https://github.com/CrunchyData/postgres-operator being a notable example that we see used quite a bit for running PostgreSQL.
I am pretty optimistic about Mesosphere’s ability to deliver a “universal operator” because they have the experience of running stateful workloads on Mesos and, well, because Florian’s blog announcing it makes a lot of sense. In other words, I have not played with it and have yet to see users on the OpenEBS community using it. Nonetheless, I definitely recommend keeping an eye on it.
KubeFlow has fast become one of the most popular projects in our broader ecosystem, with almost as many watchers or stars on GitHub as our own OpenEBS (I couldn’t resist…and to be clear KubeFlow is more broadly adopted afaik than OpenEBS so far) https://github.com/kubeflow/kubeflow. One awesome looking project that …