In Chapter 3, Building the Frontend we availed ourselves of some of the many opportunities that Microsoft Azure data service offers to developers when dealing with data. A data service should not be a constraint: it should be an opportunity to choose the best data service from many after reviewing the requirements of the solution.
We classified data services on a usage base, evaluating principles, typing, speed, and accessibility. But all data has one thing in common: it all represents the current state of an entity. We always spend a lot of time speaking about the current state.
We also introduced the concept of stale data. A distributed application contains copies or parts of the same state at different times because it is not possible to update all the instances at the same time. How do we sync all the state copies around the system? We need to introduce a couple of new kinds of data.
In this chapter, we will learn how to:
Use messaging in solutions for asynchronous...