Yes. Running multiple multi-billion row Postgres DBs on AWS Aurora.
The number of rows isn't that consequential honestly. Btrees are very fast at navigating deep hierarchies. It's the volume and complexity of traffic that matters.
On AWS Aurora we can run 10 readers to handle our peak midday traffic (10M+ daily active users).
I wouldn't shy away from doing billion row DBs on-prem if that's what the finances detail. Postgres can handle it. But the new wave of scalable Postgres (alloydb, aurora, neondb) will make it easy.
Comments
Yes. Running multiple multi-billion row Postgres DBs on AWS Aurora.
The number of rows isn't that consequential honestly. Btrees are very fast at navigating deep hierarchies. It's the volume and complexity of traffic that matters.
On AWS Aurora we can run 10 readers to handle our peak midday traffic (10M+ daily active users).
I wouldn't shy away from doing billion row DBs on-prem if that's what the finances detail. Postgres can handle it. But the new wave of scalable Postgres (alloydb, aurora, neondb) will make it easy.