Last week, I wrote an analysis of the ITEF Idempotency-Key specification. The specification aims to avoid duplicated requests. In short, the idea is for the client to send a unique key along with the request:  If the server doesn’t know the key, it proceeds as usual and then stores the responsif the server knows the key, it short-circuits any further processing and immediately returns the stored response  This post shows how to implement it with Apache APISIX.   Overview   Before starting c

Frankel's platform  covers topics related to software development, technology trends, and coding tutorials. Through articles, tutorials, and personal anecdotes, Frankel offers insights into programming languages, development frameworks, and best practices in software engineering. Readers can learn about software design principles, development methodologies, and emerging technologies to enhance their coding skills and build high-quality software applications.

A Java geek

This post explains how to implement the Idempotency-Key specification on Apache APISIX using a plugin. It covers the basic implementation, handling of the nominal path and error paths, and the potential for further improvements.

Implementing the Idempotency-Key specification on Apache APISIX