Re:How to Efficiently Choose the Right Database for Your App...
by samlambert on Sunday February 28, 2021 @11:01AM
(#26294250)
Vertical scaling and scaling out via replicas is only excusable in a world where sharding isn't a solved problem.
With a bunch of read replicas you have to deal with eventual consistency when you get replication lag as well as the inability to scale writes.
If you shard out horizontally you get write scaleability, and read scalability with much less chance of replication delay. You like likely be reading from the master node most of the time. You also gain a bunch of operational flexibility, and smaller failure domains.
Re:How to Efficiently Choose the Right Database for Your App...
by gher-shyu3i on Monday March 01, 2021 @11:56AM
(#26304834)
Don't you still have replication delay when sharding horizontally?
Re:How to Efficiently Choose the Right Database for Your App...
by mtVessel on Sunday February 28, 2021 @12:56PM
(#26295312)
How does horizontal sharding help with HA/DR concerns?
Re:How to Efficiently Choose the Right Database for Your App...
by rzzzt on Sunday February 28, 2021 @06:06AM
(#26292476)
Multi-master replication was also a MySQL-only functionality that came built in, while on Postgres you had to pick a third-party solution (I think...)? Did that change in recent times?
I would say for anyone starting out and worrying about how large a single node can scale, Postgres can run well on aa 64/128core server, 2TB ram and 20TB ZRAID6 with a chain of read replicas. This can be done out of the box on Postgres without much issue and can get many businesses quite far, but once you go to the lots and lots of TB, or you have specific write latency, consistency, or other requirements, you have to evaluate multiple databases against your company's specific usage patterns and data, as no benchmark will give you a good idea.