Problem: There are Kubernetes-based data services, virtual machine-based data services, and anynines data services. How would they coexist and how can anynines make them consumable by application developers when application developer groups own different Kubernetes clusters? It’s not only about integrating the virtual machine-based enhanced data services in Kubernetes, but it’s about central data service management.
anynines developed a second-generation integration framework that:
- Allows application developers to create their own service instances.
- Introduces the concept of service bindings.
- Integrates backup and restore framework, so that you can declaratively create backup plans and individual backups and recover them where all the actual heavy lifting happens somewhere else.
- Allows you to control your data services through your application cluster, but the data service instances they run are either as virtual machines or as Pods somewhere else.
- Allows you to create a Postgres as a pod-based version or as a virtual machine-based version.
What’s next: anynines created its own Postgres operator and it will create more operators in the near future.
This summary was written by Camille Gregory.