Really depends on many factors. If you have everything in RAM, almost nothing matters.

If your dataset outgrows the capacity, various things start to matter, based on your workload. Random reads need to have good indices (also writes with unique columns), OLAPs benefit from work_mem, >100M rows will need good partitioning, OLTP may even need some custom solutions if you need to keep a long history, but not for every transaction.

But even with >B of rows, Postgres can handle it with relative ease, if you know what you’re doing. Usually even on a hardware you would consider absolutely inadequate (last year I migrated our company DB from MySQL to Postgres, and with even more data and more complex workflows we downsized our RAM by more than half).

Postgres is so quick if you know how to use it…

Just self-host it? It’s open-source, that will last you a lifetime.

That sounds great, let me know how it works for you.

I’m not sure if this is satire, because if yes, well played, if not, Fuck That.

It’s voice and video calling with chat and screensharing. I intend to use it for a language school. It’s extendable, for instance you can also self-host a whiteboard, where everyone can draw. You can see the drawing in real time, which is good for asian languages, where direction of the stroke is important.

Free, open-source, packaged in Debian, runs without issues, used it with friends for multi-hour voice chats during gaming nights.

On the server you can configure things like FPS for screenshare. I have yet to adjust that and try streaming video/game through it.

Way too few mentions of Jitsi.

I use it with friends, it has good server config, and I’m pushing it on businesses.