Hands-On Reactive Programming in Spring 5

Conflict-free replicated data types

The bigger our application becomes, the more data it has to process, even for a single microservice with a well-defined scope. As we mentioned previously, transactions do not scale well, and with application growth, it is harder to keep the global state consistent even within boundaries of one microservice. So, for the sake of performance and system scalability, we may allow data to be updated concurrently by different service instances without a global lock or transactional consistency. Such an approach is called optimistic replication and allows data replicas to evolve in parallel with possible inconsistencies that should be resolved later. In such scenarios, consistency between replicas is re-established ...