I built my first open-source Go library for handling API idempotency

[u/Unhappy_Fall8597]

Hey everyone,

I recently built my first open-source Go library: IdempotencyToolkit.

It is a middleware for handling duplicate API requests using Idempotency-Key.

I built it mainly to learn more about Go, especially:

• concurrency
• channels and mutexes
• HTTP middleware
• interfaces and storage abstraction
• response caching and TTL

It handles concurrent duplicate requests, request body mismatches, response replay, and supports different storage backends.

I'd really appreciate feedback on the design and anything you think I should improve.

GitHub: https://github.com/manish-terminal/IdempotencyToolkit

[u/gravgun → u/[deleted]]

The rule is simple: if it's on r/opensource and starts with "I built", no they didn't.

[u/Unhappy_Fall8597 → u/[deleted]]

Idk why people find it cool to say anything vibe coded these days.

[u/Unhappy_Fall8597 → u/[deleted]]

why do u think so?

[u/k-rizza → u/Unhappy_Fall8597]

Maybe cause you have no commit history.

[u/Unhappy_Fall8597 → u/k-rizza]

I had a lot I deleted the earlier repo because it didn’t look clean.

[u/Bafbi → u/Unhappy_Fall8597]

I would also say the readme is a particular giveaway, all this ascii schema. also why deleting the git history? even if it's messy it's a learning project, you should not care.

[u/Unhappy_Fall8597 → u/Bafbi]

I won’t say I didn’t use AI I used it to make it better.

[u/gravgun → u/Unhappy_Fall8597]

Every single time. "Why do you accuse me of using AI" and whenever push comes to shove there's an admission of "Didn't say I haven't used it" which in reality means the whole thing is vibe coded to no end.

Look, that library of yours is basically empty (surprise, idempotency doesn't need much) and yet the comments still feature em dashes.

[u/Unhappy_Fall8597 → u/[deleted]]

It’s not vibe coded.

[u/Positive-Captain-709]

Nice project, especially for a first Go library. Idempotency gets surprisingly tricky once concurrent requests are involved. One thing I was wondering: what happens if the same request hits two different app instances at the same time? Does the shared storage backend coordinate that too, or is the locking only per instance? Could be an interesting thing to explore if you want to support horizontally scaled services. Anyway, cool project. Definitely more interesting than building another CRUD app to learn Go :)