Kraken.js POST handlers: choosing the layer that owns retry deduplication
Kraken.js configuration and duplicate writes I have a Kraken.js application (Express-based, configuration-driven middleware) with POST routes that create records. Clients and an upstream proxy can legitimately retry requests, and Kraken itself does not document any built-in retry or idempotency handling, so a repeated POST can reach the same route handler tw