Dealing with eventual consistency
Last year during Øredev I presented on how to deal with eventual consistency.
Quite a few people I talk to, tell me they can’t use eventual consistency, because they can’t have people looking at data that is stale. However, they don’t blink an eye when they’re adding caching into their system, which is never 100% in-sync with their persisted data and thus returns stale data. But even data that is showing inside your browser is already stale. While your application is retrieving the data, sending it to the browser and it’s being rendered, it’s not unlikely the data is already updated in the database.
I’ll be blogging more about eventual consistency in the near future. For now, be sure to watch the video and check out the demo I’ve built to show how a movie-theater website should deal with high traffic load on their webserver.
[…] Calls (RPC). Message queues remove the temporal coupling. It introduces different challenges, like eventual consistency. I mention messaging and temporal coupling because those don’t appear in the logical view of […]