---
title: "Discussion on \"Fixing duplicate API requests\" | Hashnode"
description: "Discussion on \"Fixing duplicate API requests\". The first rule of distributed systems is \"Don’t distribute your system\". Designing distributed systems right is infamously hard for multiple reasons.\nThe idempotency concept\nFor example, a call to a function can succeed or fail in non-distributed sys..."
url: "https://hashnode.com/posts/fixing-duplicate-api-requests/660e6c9af19ff49313917058"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Fixing duplicate API requests](https://apisix.hashnode.dev/fixing-duplicate-api-requests?utm_source=hashnode&utm_medium=feed)

The first rule of distributed systems is "Don’t distribute your system". Designing distributed systems right is infamously hard for multiple reasons. The idempotency concept For example, a call to a function can succeed or fail in non-distributed sys...

Apr 4, 2024 · 3 min read · apisix.hashnode.dev  
Read the article

-   [#apis](https://hashnode.com/tag/apis)
-   [#specification](https://hashnode.com/tag/specification)
-   [#rest-api](https://hashnode.com/tag/rest-api)
-   [#idempotence](https://hashnode.com/tag/idempotence)

## Written by

[Nicolas Fränkel](https://hashnode.com/@nfrankel)

@nfrankel · Geneva

  
[View profile](https://hashnode.com/@nfrankel)

Developer Advocate

Technologist focusing on cloud-native technologies, DevOps, CI/CD pipelines, and system observability. His focus revolves around creating technical content, delivering talks, and engaging with developer communities to promote the adoption of modern software practices. With a strong background in software, he has worked extensively with the JVM, applying his expertise across various industries. In addition to his technical work, he is the author of several books and regularly shares insights through his blog and open-source contributions.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
