Dealing with eventual consistency
- You'll learn what eventual consistency actually means. Both in UI and in business processes
- You'll learn how to trick the user when you need to deal with eventual consistency
- You'll not longer be afraid of eventual consistency and can explain to your business stakeholders it's not a scary thing
As software architects we want to make our systems more performant, maintainable, understandable, or any other thing-able. We use infrastructure like Azure Service Bus or Service Fabric. Maybe we'll introduce patterns like CQRS and Event Sourcing. Many of these choices introduce eventual consistency, but users expect immediate consistency. They don't want to wait for eventually. They expect feedback now. There are, however, ways to work around this. So what exactly is eventual consistency and how can we make it work? In this session, we'll have a look at different patterns, both in the user interface and the back end, that give our users immediate feedback even though the back-end system is not. We'll discuss how to solve the complexity of dealing with eventual consistency, without sacrificing decomposability or performance.