Fastify request lifecycle and Redis idempotency store: duplicate POST handling at integration boundary
Goal is to prevent duplicate writes when clients retry POST requests that pass through Fastify routes to a downstream data store. Fastify provides no built-in idempotency or retry deduplication, so the integration boundary between the request lifecycle hooks/plugins and an external dedup store must be defined by application code. Encapsulation allows scoping