Tagged articles

idempotency key

4 articles · Page 1 of 1

Sep 22, 2026 · Backend Development

Beyond Distributed Locks: Three-Layer Idempotency for Spring Boot Order APIs

The article demonstrates why distributed locks alone fail to guarantee idempotency in Spring Boot order APIs, and presents a three-layer solution combining Idempotency-Key with request fingerprinting, Redis SET NX for fast duplicate interception, and a database unique constraint as the ultimate safeguard against duplicate orders even after crashes or Redis failures.

API designDistributed LocksMySQL

0 likes · 25 min read

Beyond Distributed Locks: Three-Layer Idempotency for Spring Boot Order APIs

Yumin Fish Harvest

Sep 21, 2026 · Backend Development

Idempotency Design for Write Services: 7 Patterns & Selection Guide

This article details seven idempotency patterns for backend write operations—including unique keys with database constraints, state machines, execution records, naturally idempotent actions, request fingerprinting, client-generated keys, and server-issued tokens—with concrete examples, SQL code, and a selection guide to match each pattern to specific business scenarios like payment callbacks, order cancellations, and duplicate purchases.

backend developmentconditional updatedatabase unique constraint

0 likes · 29 min read

Idempotency Design for Write Services: 7 Patterns & Selection Guide

Chengwu Tech Stack

Sep 8, 2026 · Artificial Intelligence

From Video Analysis Pipeline to Production System: Architecture, Contracts, and Guardrails

This article details the system architecture for production-ready video AI analysis, covering task contracts with three distinct identifiers, media and model isolation, capacity estimation using Little's Law, retry and recovery rules with outbox pattern, evidence retention requirements, and a phased gray-release strategy for two scenarios: engineering quality inspection and intelligent security.

Capacity PlanningGray Releaseevidence retention

0 likes · 16 min read

From Video Analysis Pipeline to Production System: Architecture, Contracts, and Guardrails

Engineer Tang's Implementation Study Notes

Mar 9, 2026 · Backend Development

Microservice Gateway False Replay Attack Alerts: Root Cause & 3 Progressive Fixes

A microservice gateway misidentifies legitimate requests as replay attacks due to client-server time drift, causing 401 errors; the article explains the core logic, offers an emergency manual time sync, then details three progressive fixes: tiered gateway time thresholds, idempotency keys to eliminate time dependence, and internal NTP deployment for permanent synchronization.

API gatewayMicroservicesNTP

0 likes · 17 min read

Microservice Gateway False Replay Attack Alerts: Root Cause & 3 Progressive Fixes