Eventual consistency and conflict resolution Questions

Design systems that don't require global consensus but achieve eventual consistency. Understand replication strategies for eventual consistency: multi-master replication, read repair, anti-entropy repair. Handle conflicts: last-write-wins, vector clocks, application-level conflict resolution (e.g., CRDTs). At Staff level, discuss: When is eventual consistency acceptable? How do you handle the window where different replicas see different data? What's the user experience during inconsistency?