When Postgres Stops Being Enough

1. The Most Senior Database Decision Is Often Not Adding One

Somebody on your team wants to add a second database. The feature is real, the benchmark they ran is real, and the new store genuinely does that one thing better than Postgres does.

The decision still usually comes out as no, and understanding why is what this lesson is for.

A database is not a library you add to a dependency file. It is a system somebody has to operate, forever, and the cost of operating it is paid every week whether or not the feature that justified it is still important