The Multi Model Database
A multi model database supports more than one data model, such as documents, graphs, and key value, inside a single engine. Rather than running a separate database for each shape of data, you keep them together and query across them.
Why combine models
Real applications mix shapes: a product catalog reads naturally as documents, the recommendations between products as a graph, and a session cache as key value. Stitching three databases together adds operational cost and makes consistency across them hard. A multi model engine offers:
- One operational surface to deploy, back up, and secure.
- Cross model queries that join a graph traversal with a document filter.
- Shared transactions so a change spanning models stays consistent.
The tradeoffs
A general engine rarely beats a specialist on that specialist's home turf; a dedicated graph store may out traverse it, and a dedicated search engine may out rank it. Multi model wins when the simplicity of one system and the value of cross model queries outweigh peak performance in any one model.
Key idea
A multi model database serves documents, graphs, and key values in one engine, trading peak per model performance for unified operations and cross model queries.