Eventual Consistency is a UX Nightmare

Eventual Consistency is the term most people refer to when they are reading from a different data source from where they perform a write. Usually leads to a bad user experience where a user performs some action but then doesn't see their change reflected in the UI immediately. There can be many reasons for this. It could be from using a read replica that is eventually consistent. If you're using Event Sourcing with Projections as your Read Model, which is built asynchronously. Or if you're processing commands asynchronously via a message queue. 🔗 EventStoreDB https://eventsto.re/codeopinion 🔔 Subscribe:    / @codeopinion   💥 Join this channel to get access to source code & demos!    / @codeopinion   🔥 Don't have the JOIN button? Support me on Patreon!   / codeopinion   📝 Blog: https://codeopinion.com 👋 Twitter:   / codeopinion   ✨ LinkedIn:   / dcomartin   📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo... 0:00 Intro 0:39 Replication Lag 1:47 Event Sourcing Projection 2:48 Async Processing 4:53 Server Wait 6:14 Client Polling 7:12 Push to Client 8:38 Read from Primary 9:59 Multi-User #softwarearchitecture #softwaredesign #cqrs