-2

So I'm designing a write heavily system where consistency is primary concern. Assuming we have a lot of daily active users come from all over the world having one single database which capable of writing data (master-slave) would add a lot of latency. I'm considering using master-master replication model but afaik the conflict resolution is very hard to achieve when your system is write heavy, not sure if it's even possible to do so. So is it possible to have multiple database capable of write all over the world or the only way to achieve this is by trading off consistency with latency (master-slave approach). I use PostgresDB btw.

Patrick
  • 734
  • 11
  • 26
  • It depends on what types of writes your system has. If your system is almost all INSERTS, then you can have multiple write databases. If your system has a lot of UPDATES, then you have to have one master system for consistency. Design your system to minimize or eliminate UPDATES. – Gilbert Le Blanc Aug 07 '23 at 10:58

0 Answers0