Postgres for everything hits a wall the moment dashboards get concurrent

I used to say, "Just use Postgres."

After that, our dashboards became concurrent, and the read replica we quickly added to offload some of the pressure from the main database began overheating instead.

The meme that traps you

There is a reassuring notion that Postgres can handle all tasks. OLTP, queues, search, analytics, everything in a single package.

But it shouldn't be the ultimate goal.