Skip to content
DnsLister Forum

Where domain hunters compare notes

9 of the 10 most popular databases now call themselves multi-model. Define the term first, because the badge stopped separating anything

In the June 2026 DB-Engines top 10, 9 systems carry the "multi-model" tag, including MySQL, PostgreSQL, MongoDB, Cassandra, and Oracle. Snowflake is the only one that doesn't. When 90% of the top 10 carry the same tag, it stops differentiating.

I went and counted after sitting through a consolidation review. The whole case for cutting a system was "the other platform is multi-model, so we don't need this one." Their reasoning fell apart once I checked how many databases actually carry the label.

Multi-model is a storage claim, one product holds relational, JSON, graph, and vector data. Converged is a guarantees claim, one transaction boundary, one optimizer, one consistency model, and one governance domain across all of it. Most systems make the first claim but fewer show the second.

Two engines can share the data without sharing the guarantees, and vendors say so in their own docs.

MongoDB runs real multi-document ACID transactions, but its search and vector run in mongot, a separate process that's eventually consistent, so the index trails the write and nothing errors.

pgvector uses PostgreSQL's planner, but its README puts filtering after the index scan, so a narrow WHERE can leave you a fraction of the top-k you asked for.

Spanner is the one that shows the second claim. One distributed ACID transaction across models, one plan, and search that runs inside the transaction, so on consistency it's a peer, not a target. Its own docs name the limits elsewhere: no document API, no row-level security, and a static ScaNN index you rebuild as recall drifts.

You want a converged database when you need the guarantees to hold across models, not just the data to sit in one product. That shows up in two spots. In a consolidation, the checkbox can't tell you what you get to retire versus what search process is still running underneath. In an agent workload, the consistency boundary you buy is the one your agent inherits, so it reasons on whatever retrieval hands it.

Runnable tests behind each claim are in the full writeup: https://blogs.oracle.com/developers/converged-database-vs-multi-model-database-whats-the-difference

Source: r/OracleAIDB · by /u/AlexAtOracleAIDB

Leave a Reply

Your email address will not be published. Required fields are marked *