Techment — Site Header

What is Polyglot Persistence

Definition

Polyglot persistence is the practice of using multiple, different database technologies within a single application or system, choosing each store based on the data and access pattern it serves best rather than forcing every workload into one database type.

« Back to Glossary Index

Matches each workload to the database best suited to its access pattern
Improves performance by avoiding the compromises of a one-size-fits-all store
Lets relational, document, key-value, and graph data each live in their ideal engine
Supports complex applications whose components have genuinely different data needs

Real World Example

An e-commerce platform uses a relational database for orders, a document store for product catalogs, a key-value cache for sessions, and a graph database for recommendations, each chosen for its strengths.

FAQs

What does polyglot persistence mean?

It means deliberately using several different database types in one system, each selected for the workload it handles best.

Why not use a single database for everything?

Different access patterns, relational, document, key-value, graph, have different ideal stores, so one database forces performance or modelling compromises.

What is the downside of polyglot persistence?

Operational complexity rises, since teams must manage, secure, and integrate multiple database technologies.