important in atleast-once type to make sure that the double payment deduction or double increments don't happen.
no additional effect if the same endpoint is called more than once with the same input parameters.
idempotency keys which is more like a hash of the critical parameters which decide that it is an unique transaction. the target system/service should use this key to be stored in a column which has unique constraint applied at the database level.
different types of acknowledgement strategies
- atleast once
- atmax once
- exactly once
Referenced in:
All notes