Postgres is enough for more than we admit

I came across this on Hacker News and felt like I needed to share it with the dev community. The main point is simple: a lot of teams reach for extra databases, queues, search engines, caches, and services before they actually need them.

This page lays out where Postgres is usually enough, and where you may actually need something else: https://postgresisenough.dev/

Postgres is not perfect for everything, but it is good enough for a surprising amount of real-world work. The more I build and maintain systems, the more I appreciate boring infrastructure that is easy to debug, monitor, back up, and reason about.

This hit a nerve for me because I have seen stacks become harder to operate not because the product needed that complexity, but because the architecture was designed for future scale that never arrived.

Curious how others here think about this. Where do you draw the line between "Postgres is enough" and falling into the sprawl trap?