How to Store JSON in a Database Without Attracting the DBA's Attention
summary
The talk examines storing JSON in relational databases, focusing on PostgreSQL and tools like Hibernate, Spring Data and JPA. It explains problems that motivate using JSON (flexible attributes, inheritance mapping), shows how to solve them while staying within a relational schema, discusses when JSON is appropriate, and warns about practical pitfalls and why many DBA/analytics/QA concerns are now less relevant.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:27Why DBA shouldn't know
- 3:54Relational DBs and JSON
- 6:23JSON in events
- 8:29MongoDB vs PostgreSQL
- 10:11Table inheritance and JSON
- 13:45Arbitrary attributes and JSON
- 17:14Searching JSON attributes
- 20:45N+1 and Lazy loading
- 25:26Row size limits
- 27:54Large JSON in PostgreSQL
- 30:03Hibernate issues solved
- 33:20Hibernate 6 JSON support
- 35:05JSON indexing in PostgreSQL
- 37:34JSON queries with Hibernate
- 38:58Summary and tips
- 40:02Q&A
related talks
51mDealing with JSON in the relational world
47mDealing with JSON in the Relational World
48mHow Well Do Relational Database Engines Support JSON?
49mShould I use JSON in PostgreSQL?
29mRetire your tables. It's all JSON now.
03mDBTB INT Greg Rahn
14mJSON data structure – the hidden gem inside your database engine
53mThe NoSQL Store everyone ignores: PostgreSQL