Distributed Database DevOps Dilemmas? Kubernetes to the Rescue
summary
Shows a concrete integration: Apache Ignite uses a Kubernetes Service-backed IP finder that returns pod IPs so cluster nodes auto-discover and form a self-healing cluster. Uses standard Kubernetes objects and kubectl (demo on minikube scaled 2→5 pods) and Ignite’s TCP finder; persistence is supported by assigning volumes per node or StatefulSets. Works end-to-end in the demo and the same pattern applies to Cassandra, MongoDB, Redis and MySQL deployments.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:45Agenda
- 4:00Apache Ignite
- 5:58Server Nodes
- 7:12Deployment
- 8:10IP Finder
- 14:00IP Finder Implementation
- 15:58Ignite Implementation
- 17:05Deployment Demo
- 18:20Kubernetes Framework
- 19:53Deploying Cluster
- 27:28Volumes
- 29:04Why run multiple cluster nodes
related talks
33mDistributed Database DevOps Dilemmas? Kubernetes to the rescue!
59mA DevOps State of Mind: Managing Microservices + Databases with Kubernetes
32mRunning Databases in Istio's Service Mesh
41mDistributed Java DBs Under the Hood: Main Components and Interactions Between Them
31mAn Adventure in Multi Cloud with Kubernetes and Distributed Data
42mDistributed Data Stores on Kubernetes
35mStateful Apps On Kubernetes - Bring Them On!
45mDatabases on Kubernetes: Why you should care