Destination system
The destination system is intended to receive data on a particular transfer path. Reachability, receipt and completed processing are distinct states.
A destination system is the intended receiving system in a data flow. The role belongs to the particular transfer path. The same system can supply data for another path and be the source there.
Define receipt for a specific operation
In a fictional customer portal, requests to create orders go to the ERP; it is the destination there. If the ERP later sends the processing status to the portal, the portal takes the destination role. Each direction needs its own description of expected receipt.
Choose evidence of success to fit the goal
Microsoft distinguishes source and destination data stores when copying. In your application, also clarify when data counts as received or processed at the destination. A reachable endpoint does not confirm order creation. Agree on the expected feedback and check the operation through to the required destination state. The term destination system does not guarantee successful processing.
Sources
Related terms
- Source systemThe source system supplies data for a particular transfer path. That role alone does not establish who authoritatively maintains all business information.
- Interface contractAn interface contract describes the agreed data exchange. Data structure, responses and their meaning need to fit together for both sides.
- 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