Eventual consistency
Eventual consistency permits temporarily different data states that should converge under the intended operating conditions.
A state reaches other systems with a delay
Eventual consistency is a consistency model in which copies or derived views may temporarily differ. If no new changes arrive and the required transfer and processing work, they should eventually converge on the same intended state.
In a fictional example, an address has already changed in the CRM while a downstream view still shows the old one. The model alone guarantees no fixed number of seconds until the update arrives. It does not make a persistent processing failure disappear. Agree on permitted delay, detection of overdue changes and behaviour when data is stale. Whether an invoice may already be created is an additional business rule.
Sources
Related terms
- Data consistencyData consistency means that data follows defined rules and related states do not contradict each other.
- Event-driven architectureIn event-driven architecture, components report events that other components can respond to independently.
- Transactional inboxA transactional inbox uses durable message records to protect local processing against duplicate deliveries.
- Message acknowledgementA message acknowledgement tells the broker that a delivery has been received or processed according to the agreed rule.
- Retry jitterRetry jitter varies waiting times randomly to spread retries and reduce simultaneous requests from many clients.
- Test tenantA logically bounded customer context of a multitenant application, configured for testing.
Articles on this topic
APIs & Integration with ASES
ERP, CRM and shop cleanly connected