What is the difference between JSONB and a fully normalized relational schema in Postgres?

A normalized schema splits data into separate tables connected by foreign keys, with each fact stored once; a JSONB column instead stores a whole nested document as a single value inside one row, queryable with operators like ->, ->>, and @>, and indexable with a GIN index.

Normalization enforces consistency through foreign keys and makes cross-entity queries (joins) efficient, but requires a schema change whenever the shape of the data changes. JSONB tolerates a flexible, evolving shape without a migration — useful for things like a form's arbitrary custom fields, third-party API payloads you don't fully control, or settings blobs — but it trades away foreign key enforcement and makes some queries (like aggregating across a specific nested field on a very large table) less efficient than an equivalent normalized column would be.

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.

Webull! Receive free stock by signing up using the link: Webull signup.