I fully agree - there's no excuse why the DB should be falling over when I've seen a single postgres instance (with a read replica, granted) handle >1M users just fine.

Unfortunately my SQL skills haven't improved since my DB class in university, so I won't be much help. I'll be keeping an eye on the repo of course, and I can give some consulting/guidance or even open some PRs myself when they decide to implement horizontal scaling.

Yeah, I think a single postgres cluster with read replicas should be able to handle the needs of a single instance just fine. You can then horizontally scale the backend and frontend to keep up using containers.

Ideally, that instance can scale up to a few million users, and then federation can provide the horizontal scaling that takes the lemmyverse up to Reddit scale.

The backend just needs to handle databases better. Adding support for read replicas, making it more efficient, etc.

Not sure how well pict-rs scales, but that's probably pretty light already, vertical scaling might be good enough that it'll always be limited by the DB.

But yeah, I guess the worst case scenario is that Postgres doesn't scale enough and we need to switch to something like cockroachdb. Or go for snowflake uuids and noSQL like Twitter did back in the day.