Welcome to – Dasith Wijesiriwardena
summary
Explains why eventual consistency hides user-visible bugs and when choosing availability over strong consistency actually improves uptime, demonstrates concrete patterns — compensating transactions, idempotent APIs — and shows runnable examples built with .NET and Serverless architectures, including how asynchronous workflows map to business processes and where latency or lost updates show up in production, with slides and code references from real projects and clear guidance on tradeoffs and testing.
AI-written summary · about
related talks
52mEventual Consistency in a Stateful Service
18mNoSQL, YesCosmos: Build that Eventually Consistent Application using Azure Cosmos DB
38mEventual Consistency: A Question of Time and Expectations
01h 01mLost in transaction Strategies to manage consistency in distributed systems
52mGoing eventually consistent with CQRS
25mGrowing Distributed Systems
42mApplication Architectures: The shadows and highlights of Event Driven Design
44mDistributed systems and scalability rules