Latest posts
-
Rate-Limit Playbook: What to Limit First
Outbound provider APIs first, then auth endpoints, then your own API, then worker concurrency. With the bucket sizes and thresholds we actually run.
-
Webhook Idempotency: The Five-Line Habit That Prevents Double Charges
A unique constraint on the provider event ID, checked before any side effect, turns guaranteed duplicate webhook delivery into a harmless no-op.
-
Staying Under Rate Limits with Client-Side Backpressure
Use local queues and header-driven throttling to keep outbound calls inside provider limits without dropped work or cascading failures.
-
Circuit Breakers for Vendor API Outages
Circuit breakers stop repeated calls to a failing vendor endpoint from cascading into your own timeouts and resource exhaustion.
-
Handling Rate Limits with Exponential Backoff in Node.js
Build retry logic that respects API rate limits by combining exponential backoff, jitter, and idempotency so transient failures do not cascade.
-
How to Implement Idempotent Webhooks with Postgres Unique Constraints
Use Postgres unique constraints on provider event IDs to deduplicate webhook deliveries reliably at the database layer.
-
Resilient API Workflows: Retries, Idempotency, Rate Limits, and Webhooks
Timeouts and backoff, idempotency keys, proactive rate-limiting, signed and deduped webhooks, ahead-of-expiry OAuth – integrations that survive production.