Data inconsistency
Data inconsistency is a condition in which related data or representations of the same information disagree or violate rules requiring them to agree.
Microservices Patterns, Second Edition
A condition in which representations of related data differ across services or components that should agree.
- How it is used
- Explains data inconsistency as a consequence of complex requests spanning services in a fine-grained architecture.
- How deep it goes
- Traces bugs to complex cross-service interactions and notes Saga use, but does not detail the Saga pattern.
- Examples
- Uses unassigned couriers and missing refunds after immediate order cancellations as inconsistent outcomes.
- What you can do after
- Understand how complex cross-service interactions can produce hard-to-diagnose inconsistencies.
Read how Microservices Patterns, Second Edition explains data inconsistency →
Spring Start Here, Second Edition
A data inconsistency is a condition in which related stored or exchanged data does not agree or satisfy the application's consistency rules.
- How it is used
- Motivates transactions as protection against partial changes in multi-step application operations.
- How deep it goes
- Defines inconsistency through failed transfers and explains commit and rollback, but stops short of Spring implementation details.
- Examples
- Uses a wallet transfer with failed account updates and REST endpoint calls that may fail.
- What you can do after
- Understand how committing or rolling back a transaction can prevent partial changes from leaving data inconsistent.
Read how Spring Start Here, Second Edition explains data inconsistency →
Also covered in
- Grokking Software ArchitectureIn early access (MEAP)
Related concepts
- database transactionaddressed by · A database transaction is a bounded unit of database operations whose changes are treated as one logical whole, typically committed or rolled back together.
- event sourcingaddressed by · Event sourcing is a persistence pattern in which state changes are recorded as an ordered sequence of events from which current state can be derived or reconstructed.
- split-brainproduced by · Split-brain is a distributed-system failure state in which disconnected nodes or groups independently act as authoritative and may make conflicting decisions or writes.
- optimistic concurrency controladdressed by · Optimistic concurrency control is a concurrency-control technique that allows operations to proceed with limited locking and detects conflicting changes through validation before committing updates.
- feature flagaddressed by · A feature flag is a configuration control that conditionally enables, disables, or selects software functionality at build time or runtime.
Questions about data inconsistency
What is data inconsistency?
Data inconsistency is a condition in which related data or representations of the same information disagree or violate rules requiring them to agree.
Which Manning books explain data inconsistency?
Microservices Patterns, Second Edition and Spring Start Here, Second Edition.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

