News for hackers. Stuff that matters.
Re:Postgres scaling advice by __s on Tuesday January 26, 2021 @09:01AM (#25915812)
To back up how far one server can go, Stack Overflow used a single database for a long time

https://nickcraver.com/blog/2016/02/17/stack-overflow-the-ar... (2013 post had much less redundancy, but even their 2016 architecture is pretty undistributed in terms of being able to recreate everything from the single source of truth database)

Re:Postgres scaling advice by bcrosby95 on Tuesday January 26, 2021 @11:00AM (#25917291)
Yeah, it's been a while since I've been in a high traffic situation, but back in the late 00s we had a couple sites with 3-5 million daily unique users. Each site had a single master, a couple read replicas, and some queries were cached in memcached.

The problem in MySQL we eventually ran into was the read replicas fell behind master during peak load (by 30-60 minutes depending upon the day). So we still had to hit the master for certain queries. I left before we took the next step to fix this issue.