# The crushing success of relational databases

DevFeed: [The crushing success of relational databases](<https://devfeed.tech/articles/the-crushing-success-of-relational-databases-5768.md>)

Original publisher: [Read original article](<https://neon.com/blog/relational-databases-success>)

Author: Andy Hattemer

Published: 2024-08-13T20:27:05Z

Content type: opinion

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [Databases](<https://devfeed.tech/topics/databases.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [Hadoop](<https://devfeed.tech/topics/hadoop.md>), [Graphs](<https://devfeed.tech/topics/graphs.md>)

Tags: [databases](<https://devfeed.tech/tags/databases.md>), [graphs](<https://devfeed.tech/tags/graphs.md>), [hadoop](<https://devfeed.tech/tags/hadoop.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [relational-databases](<https://devfeed.tech/tags/relational-databases.md>), [sql](<https://devfeed.tech/tags/sql.md>)

## AI overview

The article argues that relational databases remain dominant because they repeatedly absorb capabilities associated with competing data models and query systems. It presents document, vector, and graph functionality as features that can coexist within a relational database, and revisits arguments that the relational model will continue to outlast attempted replacements.

## Source excerpt

Every once in a while, a revolutionary product comes along and changes everything. And today, we're talking about three of these phenomenal products. The first one is a document store. The second is a vector database. And the third is a graph database. So, three things: document...