Comments on: On Eventual Consistency– Interview with Monty Widenius. Trends and Information on AI, Big Data, New Data Management Technologies, Data Science and Innovation. Thu, 30 Jul 2020 10:08:53 +0000 hourly 1 By: Jonathan Gennick Fri, 26 Oct 2012 12:17:31 +0000 Monty’s comment about not handing out money when communications are down caught my eye. Believe it or not, once my local bank just handed out money. I live in a very small town. People tend to know each other. Shortly after moving here from a large city, I walked into my bank to withdraw some pocket money. I wanted $40, I think, or maybe $60. The teller told me their communications were down, and they couldn’t use their computers. She handed me the cash without making me fill out any forms, without even checking my identification. I’m not even sure she asked my name. (She must have recognized me). She did make a note so she could record the transaction later. I was pretty stunned at the time. Small-town living, I guess. Not sure they would do the same today, but twelve years ago it really happened. And yes, she did remember to record the transaction later.

By: dwight Wed, 24 Oct 2012 20:39:20 +0000 It really depends on the use case.

For example you want strong consistency for these:
– new user registration, “pick your username”. you don’t want two users to end up with “joe123″ username ever.

Eventual consistency use case:
– logging. i want the log even if not immediately readable and i may not want to fail just because of logging.

The other nuance with eventual consistency is the developer must keep the semantics in mind at all times. In QA you may not see any lag manifest so be sure to test the non-immediate case in QA when going that route.