You Don't Need Redis book cover

You Don't Need Redis

PostgreSQL Performance Optimization for Developers Who'd Rather Not Manage Another Service

19 chapters · 7 programming languages

Start reading
This is not a hardware problem. It is not a budget problem. It is a knowledge problem. And knowledge problems, if you'll permit me, are the very best kind — because they are solved by learning, not by spending.
The database was not slow. It was being asked poorly.
The ORM didn't cause the problem. It prevented the discovery of the solution.
The advice to add more services arrives most enthusiastically from those who sell them.
PostgreSQL is not a database. It is an ecosystem that most teams use as a database.
Depth produces mastery. Breadth produces familiarity. Mastery solves problems at three in the morning. Familiarity consults the documentation.
A well-run establishment does not employ three waiters where one suffices. The coordination overhead alone would be untenable.
The planner is a remarkably sophisticated instrument. It does, however, require honest information.
In infrastructure, boring is the highest compliment available.
It is not your fault. But it is, if you'll permit me, now your responsibility.

Table of Contents

Foreword — The Groundskeeper

Part I: The Problem

Part II: The Solution

Part III: In Your Framework

Part IV: The Scaling Journey

Part V: What to Do About It

Appendices

What's Next — You Don't Need Elasticsearch