Fully agree.

Postgres is a power tool usable for many many use cases - if you want performance it must be tuned.

If you judge Postgres without tuning it - that's not Postgres being slow, that's the developer being naive.

> If you judge Postgres without tuning it - that's not Postgres being slow, that's the developer being naive.

Didn't OP end by picking Postgres anyway?

It's the right answer even for a naive developer, perhaps even more so for a naive one.

At the end of the post it even says

>> Having an interface for your cache so you can easily switch out the underlying store is definitely something I’ll keep doing

He concluded postgresql to be fast enough, so what's the problem?

IOW, he judged it fast enough.