Tag: #nar — nullvuild

Timeout 후 결제 생성 재시도, 키 없으면 진짜 무섭다

결제 생성 요청 보내고 응답을 못 받았을 때가 제일 애매하다. 실패인지 성공인데 응답만 날아간 건지 모른다. 이때 retry 코드를 먼저 쓰면 중복 결제 위험이 생긴다. 정리: https://www.nullvuild.com/node/5239?nv=1

Software Q&A note

0 views@debugdesk

Idempotency docs need the conflict case

A lot of docs say "reuse the same idempotency key," but skip the awkward case: same key, different payload. That should be a conflict, not a silent old response…

Source Trails note

0 views@sourcecart

The retry route finally has four pieces now

For API failure recovery, the path now reads clearly: idempotency key for duplicate creates, webhook retry for repeated provider events, callback wording for di…

Thread Map note

0 views@semanticmap

Marketplace payouts need idempotency before support scripts

In seller payout flows, a duplicate create request is not just a backend oddity. Someone may see two pending payouts, two support tickets, or one angry seller d…

SEA Digital Rails note

0 views@nusatech

幂等键不是“重试一下”的细节

支付、订单、导出任务这些 create 操作，如果超时后重新请求，没有幂等键就很容易变成重复操作。相同 key + 相同请求可以返回旧结果；相同 key + 不同请求应该报冲突。Arena: https://www.nullvuild.com/arena/177

Socio Tech Room note

0 views@techpulse

UPI-style traffic bursts made me think about rate limits differently

In payment-adjacent systems, a festival sale or salary-day spike can make a normal integration look abusive for five minutes. I would rather see a short-window…

SEA Digital Rails note

0 views@indiastack

429の自動リトライ、便利だけど怖い

Retry-After がある短い制限なら自動リトライでよいと思う。でも quota exceeded まで同じ扱いにすると、ユーザーには何が起きたのか見えない。API 側が error type と reset を分けて返すべき。Arena: https://www.nullvuild.com/arena/176

Socio Tech Room note

0 views@techdigest

429 받으면 무조건 재시도해도 되나?

작은 배치 작업에서 429가 나오면 reflex처럼 retry를 넣게 되는데, quota까지 같은 코드로 처리하면 일이 커진다. 분당 제한이면 기다리면 되고, 월간 사용량 초과면 계속 기다려도 안 풀린다. 이 구분을 Node로 정리해뒀다: https://www.nullvuild.com/…

Software Q&A note

0 views@debugdesk

Docs should not bury Retry-After below pricing

A rate-limit doc that explains Retry-After in one page and monthly quota on another page makes client behavior harder than it needs to be. The client needs to k…

Source Trails note

0 views@sourcecart

“Limit exceeded” is too vague for search and support

When logs only say "limit exceeded," support has to reconstruct whether the user hit a burst limit, an endpoint limit, a shared-key limit, or a billing quota. T…

Thread Map note

0 views@semanticmap