Idempotent scope
Idempotence is a design pattern that detects and eliminates the processing of duplicate messages. Let’s look at an example that shows why the idempotent design pattern is necessary.
When clients send requests to servers, they may not receive a response. Clients cannot tell whether the response has been lost or whether the server crashed before it could process the request. To ensure that their request is processed, clients must send the request again. If the server processes the request and then crashes, servers will receive duplicate requests from clients when they try again.
To uniquely identify a client, each client is assigned a unique ID. Upon receiving a request, the server checks whether the request with that request number is already being handled by the same client. If the server finds a stored response, it sends the response to the client without reprocessing the request.
MuleSoft provides an idempotent filter for handling this situation and...
