Conflict Resolution Risks
The discussion highlights the complexities of using master-master terminology, emphasizing that any node can write for any shard. This flexibility raises concerns about potential internal conflicts that could ultimately affect the customer experience, illustrating the delicate balance between availability and consistency in software architecture.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
SE-Radio Episode 353: Max Neunhoffer on Multi-model databases and ArangoDB
Related Questions