In this installment of our “Patterns of Service-oriented Architecture” series, we’re going to talk about a complex concept called idempotency, and a technique you can apply to your service design to ensure that requested work is only performed once. Intent Prevent duplicate requests by allowing the Consumer of a Service to send a value that represents the uniqueness of a request, so that no reques
![Patterns of Service-oriented Architecture: Idempotency Key | Stitch Fix Technology – Multithreaded](https://cdn-ak-scissors.b.st-hatena.com/image/square/fb940702ca9ca36602ba2b7d393ca5b096982e4c/height=288;version=1;width=512/https%3A%2F%2Fmultithreaded.stitchfix.com%2Fassets%2Fimages%2Flogomark-linkedin.jpg)