Data conflict resolution is not a simple backend detail in modern enterprise systems, particularly when supporting complex concurrent operations. It is a full-stack architectural matter that affects consistency, UX, observability, and trust in the system.
We experienced this firsthand while building a government system that handled claims adjudication. Multiple case workers accessed and edited the shared records in parallel, and the premise that all system parts could be operated separately started to break down. Locking was no longer a database concern; it became a product at that scale.