✳flâneur — a map of the web's best reading

Making retries safe with idempotent APIs

aws.amazon.com · 3,115 words · saved by 1 readers

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies. If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.” Essential cookies are necessary to provide our site and services and cannot be deactivated. They are usually set in response to your actions on the site, such as setting your privacy preferences, signing in, or filling in forms. Performance cookies provide anonymous statistics about how customers navigate our site so we can improve sit

references-details-empty Skip to main content The Amazon Builders' Library Overview Authors FAQs Making retries safe with idempotent APIs Send me updates Introduction Retrying and side effects Reducing client complexity Retries and semantic equivalence Late arriving requests Same client request ID, different intent Conclusion Introduction By Malcolm Featonby | PDF At Amazon, we often see patterns in our services in which a complex operation is decomposed into a controlling process making calls to a number of smaller services, each responsible for one part of the overall workflow. For example,

Explore this link on the map →

related reading