Data consistency
Data consistency means that data follows defined rules and related states do not contradict each other.
Which rules must the data satisfy?
Data consistency describes the absence of contradictions under defined rules. It can concern relationships within one system or corresponding information across systems. In a fictional example, a delivery address's postal code must fit the stated country; two individually valid fields can still be wrong together.
Reconciliation between systems needs rules for mapping, conversion and permitted delay. Normalised spelling may look different from the source. Consistency therefore does not require identical strings or row counts everywhere. Nor does it prove that an address is correct in reality. Record which business relationships and data state the check covers.
Sources
Related terms
- Data mappingData mapping defines how source data enters a target structure. Field names, meaning, units and error handling all need to fit.
- Eventual consistencyEventual consistency permits temporarily different data states that should converge under the intended operating conditions.
- 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