You Don't Need MongoDB book cover

You Don't Need MongoDB

PostgreSQL Documents for Developers Who'd Rather Not Maintain Another Database

21 chapters · 21 methods · 7 languages · 6 parts

Start reading
Two databases is not twice the capability. It is twice the responsibility.
The most underused capability in any database is the one that arrived quietly and never insisted on attention.
A service added is a service maintained. The question is never whether the service is excellent. It is whether the service is required.
A sync pipeline, when you examine it honestly, is an admission that your data belongs together but your databases do not know it.
Did you add a second database because PostgreSQL could not store your documents, or because no one had shown you that it could?
Simplicity is not a limitation. It is the result of having enough in one place.
One spends the evening in the kitchen so that the guests may dine in the dining room.
Magic impresses. Understanding endures.
MongoDB re-executes the pipeline on every request. Gold Lapel remembers it.
Before you add a service to your stack, exhaust the one you already own.

Table of Contents

Foreword — The Groundskeeper

Part I: The Problem

Part II: Documents in PostgreSQL

Part III: The Gold Lapel API

Part IV: What You Gain

Part V: From There to Here

Part VI: In Practice

Back Matter

Waiterisms — Bonus