designing for eventual consistency

hey folks, ive been thinking a lot about systems that dont require strict ACID transactions. when we move away from immediate consistency, how do you approach designing your data models and application logic? specifically, what patterns or strategies do you find most effective for handling potential data conflicts or stale reads in an eventually consistent world? curious to hear your war stories and solutions.