> Markdown version of [/videos/382-kubernetes-and-microservices-with-multi-model-databases?t=1648](https://www.wearedevelopers.com/videos/382-kubernetes-and-microservices-with-multi-model-databases?t=1648). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Kubernetes and Microservices with Multi-Model Databases

Stop deploying separate data stores for every microservice. A converged multi-model database native to Kubernetes eliminates data silos and guarantees exactly-once message delivery without two-phase commits.

- **Speakers:** [Wei Hu](https://www.wearedevelopers.com/@wei-hu)
- **Event:** World Congress 2022
- **Published:** June 15, 2022
- **Duration:** 29:30
- **URL:** https://www.wearedevelopers.com/videos/382-kubernetes-and-microservices-with-multi-model-databases

## Summary

This session explores the intersection of Kubernetes, microservices, and multi-model databases, specifically highlighting the "converged database" approach. Countering the popular strategy of deploying separate single-purpose data stores for distinct data types, a multi-model database unifies relational, JSON, graph, and spatial workloads into one general-purpose engine. This significantly lowers operational complexity by preventing fragmented data silos and eliminating unnecessary data movement. A compelling organizational insight is how in-database containerization—enabling private "pluggable databases" within a single physical container—gives each microservice its own independently managed data layer while still allowing for centralized backups and overhead reduction.

To make this database infrastructure a native part of the Kubernetes ecosystem, teams can integrate custom container images and open-source Helm charts compatible with enterprise distributions. By leveraging standard frameworks, organizations achieve deep observability through Prometheus metric exporters, Loki log aggregation, and custom Grafana dashboards. Furthermore, deploying a dedicated Kubernetes Operator enables developers to manage database lifecycles directly via standard `kubectl` commands. Because this operator utilizes multiple backends, it gracefully orchestrates databases regardless of whether they inhabit the same internal cluster, operate in an autonomous cloud configuration, or reside in an external on-premises data center.

Transitioning mission-critical microservices to Kubernetes typically introduces severe transactional complexities, leading to a high failure rate in distributed architectures. To stabilize these architectures, native distributed transaction support is being integrated directly into container orchestration environments, accommodating both strictly consistent XA transactions and eventual consistency via the saga orchestration pattern. By combining these capabilities with built-in transactional event queues, developers can seamlessly rely on the "transactional outbox" architecture. This robust pattern guarantees that database updates and asynchronous message publishing execute together as a single atomic operation, yielding exactly-once message delivery without the performance friction of two-phase commits.

**Keywords:** converged database architecture, multi-model databases, kubernetes database operator, pluggable databases, database containerization, prometheus metrics integration, grafana observability dashboards, microservice distributed transactions, saga orchestration pattern, transactional event queues, transactional outbox pattern, idempotent message consumers, data as a microservice, event-driven microservices, exactly-once delivery semantics

## Chapters

1. **Introduction to converged multi-model data architectures** (00:14) — Using multiple database variants creates management friction whereas a single converged engine supports multiple data types without operational complexity.
1. **Evaluating performance characteristics of multi-model databases** (02:38) — Analyzing operational benchmarks reveals that converged database engines routinely outperform single-function specialized databases across diverse transaction types.
1. **Deploying mission-critical databases within container infrastructures** (03:57) — Transitioning database nodes onto scalable orchestration engines requires containerization strategies enabling developers to easily customize core infrastructure manifests.
1. **Extracting native database metrics within Kubernetes environments** (06:46) — Monitoring distributed database performance effectively utilizes specialized telemetry extensions surfacing detailed storage metrics inside standard visualization tools.
1. **Managing heterogeneous deployment lifecycles via Kubernetes operators** (10:04) — Controlling database instances scattered across hybrid hosting environments simplifies greatly when utilizing infrastructure operators exposing standardized deployment commands.
1. **Providing distributed transaction support in microservices clusters** (14:58) — Deploying critical workflows safely inside Kubernetes necessitates integrated transaction managers mediating strong and eventual consistency protocols natively.
1. **Managing application isolation via pluggable database models** (18:11) — Reducing storage friction for independent microservices requires pluggable layer abstractions virtualizing discrete databases over one unified administrative footprint.
1. **Exposing database structures as standard REST APIs** (22:13) — Creating flexible integration boundaries accelerates application development by automatically exposing internal storage logic via accessible web endpoints.
1. **Loosely coupling workflows using native event queues** (23:00) — Built-in transactional messaging components deliver guaranteed event execution consistency to safely scale distributed operations without lost packets or duplicated transmissions.
1. **Avoiding boilerplate microservices coordination using database design** (25:46) — Embedding state synchronization deeply within the persistence layer systematically simplifies sophisticated integration patterns including transaction outboxes and saga compensations.
1. **Exploring microservices capabilities via interactive cloud workshops** (27:28) — Validating advanced deployment principles becomes easier when working directly with pre-integrated code examples hosted within standardized automated lab environments.
1. **Connecting converged databases with Elasticsearch frontend interfaces** (28:42) — Large scale implementations integrate backend storage efficiently serving directly behind elastic cluster interfaces for optimized distributed search functionality.

## Related Moments

- [Modern improvements driving database adoption in Kubernetes](https://www.wearedevelopers.com/videos/255-databases-on-kubernetes) (from "Databases on Kubernetes")
- [Boosting developer productivity via consolidated converged database architectures](https://www.wearedevelopers.com/videos/632-crypto-secure-data-management-with-in-database-blockchain) (from "Crypto-secure Data Management with In-Database Blockchain")
- [Modern application stacks and real-time data requirements](https://www.wearedevelopers.com/videos/806-leveraging-real-time-data-in-fsis) (from "Leveraging Real time data in FSIs")
- [Transitioning from monolith architectures to microservices and Kubernetes](https://www.wearedevelopers.com/videos/108-get-ready-for-operations-by-pull-requests) (from "Get ready for operations by pull requests")
- [Comparing managed database services against native Kubernetes deployments](https://www.wearedevelopers.com/videos/74-databases-on-kubernetes-why-you-should-care) (from "Databases on Kubernetes: Why you should care")
- [Shifting mindsets on running databases in containers](https://www.wearedevelopers.com/videos/74-databases-on-kubernetes-why-you-should-care) (from "Databases on Kubernetes: Why you should care")

## Related Articles

- [Making Data Warehouses Fast: A Developer’s Story](https://www.wearedevelopers.com/magazine/107-making-data-warehouses-fast-a-developer-s-story)
- [Why Event-Driven Architecture Isn’t About Speed (and When You Actually Need It)](https://www.wearedevelopers.com/magazine/745-why-event-driven-architecture-isn-t-about-speed-and-when-you-actually-need-it)
- [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production)
- [Learning Kubernetes made easy with KubeCampus](https://www.wearedevelopers.com/magazine/348-learning-kubernetes-made-easy-with-kubecampus)

## Related Jobs

- [Data Scientist](https://www.wearedevelopers.com/jobs/ext/1351648-data-scientist) at **Almedia**
- [Platform Engineer (DevOps)](https://www.wearedevelopers.com/jobs/48264-platform-engineer-devops) at **WDW Consulting GmbH**
- [Devops Engineer](https://www.wearedevelopers.com/jobs/ext/1940926-devops-engineer) at **Bitpanda**
- [Platform Engineer - Mercury Runtime Platform](https://www.wearedevelopers.com/jobs/ext/293235-platform-engineer-mercury-runtime-platform) at **Raiffeisen Bank International AG**
- [Lead Cloud DevSecOps Engineer - Kubernetes](https://www.wearedevelopers.com/jobs/ext/1659167-lead-cloud-devsecops-engineer-kubernetes) at **BWI GmbH**
- [Platform Engineer (f/m/x) - Mercury Runtime Platform](https://www.wearedevelopers.com/jobs/48266-platform-engineer-f-m-x-mercury-runtime-platform) at **Raiffeisen Bank International AG**