3 ms·
> ...providing all the advantages of NoSQL JSON document stores, while providing higher performance and richer functionality (such as native joins, and ACID gua
by leereeves 12y ago
> ...providing all the advantages of NoSQL
JSON document stores, while providing higher performance
and richer functionality (such as native joins, and ACID
guarantees instead of BASE consistency)
Seems too good to be true.
The performance impact of inserting/fetching multiple rows per object, multiple SQL joins for a single logical join, etc. would probably be significant. And indexing these tables seems to require indexing every name/value pair, not just the interesting fields. And, of course, the overhead of the translation layer itself.
Also, are relational native joins and ACID guarantees still available at scale?
- lucian1900 12y agoNot sure about this paper, but Postgres' JSONB is quite good. It's quite fast, you can easily use values like SQL sub-queries and you can index both everything and also specific subsets of the JSON data with expression indexes.
- leereeves 12y agoThat's native support for the data type; this paper is about a translation layer that sits on top of the DB.