> Consider a beefy AF bare metal SQL server, see how far that gets you. Yep, this is of course the default - although you'll at least want replication for avai

> Consider a beefy AF bare metal SQL server, see how far that gets you. Yep, this is of course the default - although you'll at least want replication for availability and disaster recovery, but that's not too bad with PG/RDS. > they don't just let you drop them in as a scalable replacement for an existing usage pattern, and usually sharding starts first coming up when you're at a huge scale and already have a ton of app code and database design but have grown past what a single db can support I think once you get beyond what fits on one primary box, you're almost certainly at the point of rethinking your data access models anyway. Manual sharding is disruptive too.