Idempotency key
Related service Website & online shop
DEFINITION
An idempotency key is a client-generated unique identifier (usually a UUID) sent in a request header (Idempotency-Key) on every state-changing POST, PUT, or DELETE. Payment APIs (Stripe, Adyen, SimplePay, PayPal) use it to guarantee that if the same key arrives twice (because the network dropped, the client retried, the load balancer retried), the operation runs exactly once and the second response is the cached first response. Without it, a client retrying after a 30-second timeout charges the customer 100 thousand forints twice. Retry logic must not exist without an idempotency key on the payment, order placement, email send, and webhook delivery layers. Worth doing on your own API too: put a Postgres unique index on the key, and de-duplicate either at the call boundary or on the event queue.
- SSR (Server-Side Rendering)→
HTML rendered by the server per-request, fresh for every user. Ideal for dynamic content (dashboards), but slower than SSG.
- SSG (Static Site Generation)→
Pages are produced at build time as HTML and served from a CDN. Near-zero TTFB. DField's own site runs this way across 111+ pages.
- ISR (Incremental Static Regeneration)→
SSG + timed regeneration: the HTML is static but regenerates on a schedule. Ideal for blog content · freshness with CDN speed.
- Edge rendering→
Code runs at the CDN edge closest to the user (Cloudflare Workers, Vercel Edge). Dynamic responses with ~10–50 ms TTFB.
- RSC (React Server Components)→
React components that run exclusively on the server and never ship to the browser. Result: less client-side JS and faster hydration.
- LCP (Largest Contentful Paint)→
Time until the largest visible element paints. Google Core Web Vitals passes under 2.5s · we usually land marketing pages under 1s.