Dealing with eventual consistency
summary
Covers practical strategies for handling eventual consistency in web apps using message queues like Azure Service Bus or plain queues to accept requests immediately, with provisional UI rows stored in localStorage or IndexedDB and reconciliation via unique IDs when background workers (CQRS and Event Sourcing) process large message volumes. Compares polling, long-poll/SignalR-style notifications, and cross-server caching, and gives guidance on when to show a spinner versus a provisional success to avoid misleading users.
AI-written summary · about
chapters (17)
- 0:00Eventual consistency intro
- 3:36Ticket sales history
- 6:51Relational DB problems
- 9:21What is eventual consistency
- 11:09Eventual consistency issues
- 13:36Handling eventual consistency
- 17:36Local storage for UX
- 20:07Spinners in feedback
- 23:21Service buses messaging
- 26:12Breaking down monolithic DBs
- 27:40Amazon checkout UX
- 30:11Event sourcing solution
- 31:59Inventory with eventual consistency
- 33:49Stock perception tricks
- 35:16Hybrid ticket systems
- 37:29Stakeholder collaboration
- 38:53Balancing UX and business
related talks
51mDealing with eventual consistency
25mThe shell game called eventual consistency
01h 11mEmbracing Messaging and Eventual Consistency in your Microservices Solutions
01h 01mMessage Brokering and Event Driven Architecture on Azure
46mDIY Async Message Pump: Lessons from the trenches
55mImplementing scalable messaging patterns in Azure
57mEvent driven architectures on Azure
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
