Dealing with JSON in the relational world
summary
Compares JSON storage across MySQL, Postgres, MongoDB and Oracle, showing concrete tradeoffs: MongoDB supports streaming and client‑side binary decoding, MySQL’s BJSON allows partial updates and caps at ~1GB, Postgres’ jsonb tops ~255MB, Oracle uses Oracle OOne binary format with version tags and client decoding and a 32MB practical limit. Demonstrates a working JSON relational duality that maps single JSON documents to multiple relational tables for reads/writes, uses SODA/REST Data Services and Java frameworks, and recommends Testcontainers for DB testing.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:43Why store JSON in a DB
- 7:37JSON persistence options
- 10:17SQL standard for JSON
- 14:18Comparing JSON formats
- 29:49JSON duality views
- 44:07Free resources and tools
related talks
47mDealing with JSON in the Relational World
45mHow Well Do Relational Database Engines Support JSON?
44mWho is Jason, and what’s he doing in my database?
15mPlug-and-Play for JSON and MongoDB Developers
42mHow to Store JSON in a Database Without Attracting the DBA's Attention
50mSQL, JSON, and Java
29mRetire your tables. It's all JSON now.
14mJSON data structure – the hidden gem inside your database engine