Idempotence and 5 considerations

Idempotence-a commitment (rather than implementation) to the external interface of the system. It guarantees that the impact of multiple external calls on the system is consistent as long as the interface is successfully called.

An interface declared as idempotent will deem the external call failure as normal, and retry after the failure.

1. Query and deletion are generally idempotent.
2. Update and insert depends on the situation
3. For BS applications, pay attention to the influence of the POST method on idempotence, at least prevent repeated submission during refresh.
4. We recommend that you use the rest SOA architecture in get mode to ensure idempotence.
5. For schedul (scheduled tasks, scheduled tasks, and worker) Cluster environments, maintaining idempotence is a technical point and there are many mature frameworks to solve.
6. ......