SE-Radio Episode 353: Max Neunhoffer on Multi-model databases and ArangoDB

Native vs Layered

Max Neunhoffer explains the distinction between native and layered multi-model databases, emphasizing the advantages of ArangoDB's native approach. In a native multi-model database like ArangoDB, all data models are integrated within the same core, using a unified query engine and optimizer, which eliminates redundancy and enhances performance 1. In contrast, layered databases stack different data models on top of a fundamental one, often sacrificing performance for architectural neatness 2.

What it makes it native is that the three data models we support are all implemented in the same core with the same query engine and optimizer, and don't need any kind of redundant store or separation of concerns.

--- Max Neunhoffer

This integration allows ArangoDB to efficiently manage document, key-value, and graph models without the need for separate data stores.

   

Supported Models

ArangoDB supports three key data models: document, key-value, and graph, which are seamlessly integrated to avoid redundancy and enhance performance. Max highlights that these models fit well together, allowing for efficient data storage and querying without the need for multiple data stores 3. This integration reduces operational costs and complexity, as it eliminates the need for maintaining separate systems for each data model 4.

You have the flexibility of data modeling and the high performance for your queries, and yet you don't need three different data stores, but maybe get away with one or maybe two.

--- Max Neunhoffer

By using a single database system, ArangoDB simplifies data management while ensuring high performance and flexibility.