Event ID
An event ID identifies an event within an agreed scope. A repeat delivery needs to be distinguished from a new event.
An event ID identifies a particular event, such as a change to an order. Its uniqueness depends on the agreed scope. An order number alone is insufficient: several different events can occur on the same order.
Separate the event from its delivery
In a fictional portal, an order's delivery address changes. The corresponding notification reaches the ERP twice. These are two deliveries of the same change. A subsequent address change is a new event and needs its own identifier under the agreed rules.
Check uniqueness within the right scope
CloudEvents 1.0.2 requires uniqueness for the combination of source and event identifier, namely source and id. Agree how repeat deliveries are identified and how long processed identifiers are taken into account. An ID alone does not prevent the same change from being applied twice. Nor does it confirm that the ERP has completed the operation successfully.
Sources
Related terms
- Correlation IDA correlation ID links related messages within an operation. It can cover several events and does not replace duplicate detection.
- Idempotency keyAn idempotency key identifies retries of the same intended request. Scope, retention and API rules determine its effect.
- 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