3 ms·
> Consider a beefy AF bare metal SQL server, see how far that gets you. Quite far, possibly to millions of users. Case in point: StackOverflow runs on SQL Ser
by branko_d 4y ago
> Consider a beefy AF bare metal SQL server, see how far that gets you.
Quite far, possibly to millions of users.
Case in point: StackOverflow runs on SQL Server.
- alexvoda 4y agoActually it can vary "from not that" far to "all the way" (StackOverflow). It depends very much on the schema and the type of workload. But in general people really underestimate how far an RDBMS can take you.
- dalyons 4y agoYes and no - I think people also underestimate how miserable running a single giant RDBMS can be. Everything gets hard and dangerous - backup/restores, upgrades, online migrations & schema changes. Adding the wrong index can easily brings the whole thing down. They are complicated beasts that get very fragile at the large end (size+throughput)
- ComodoHacker 4y agoSpeaking of backups, how do you get consistent backup of a sharded DB? Not everything is sharded, some data are replicated and should be consistent. Everything becomes fragile at the large end.
- dalyons 4y agowell im comparing it to a natively distributed database, like for eg dynamoDB. I've worked with truly massive dynamodb "instances" and you really dont have to do much, they arent fragile, they just work. I don't necessarily know how their backup system works under the hood, but it backs up to a consistent point in time.
- KptMarchewa 4y ago"millions of users" are vastly different scales with different use cases. StackOverflow is mostly serving cached content.