"Exponential backoff with jitter: retries in TypeScript" by Sascha Mirow-Stanitzok
#aws-lambda #serverless #amazon-sqs #amazon-dynamodb #typescript
#aws-lambda #serverless #amazon-sqs #amazon-dynamodb #typescript
Exponential backoff with jitter: retries in TypeScript
Exponential backoff with jitter in TypeScript: build retries with a time budget and Retry-After, and prepare for the new AWS SDK defaults in November.
community.aws
October 30, 2026 at 9:30 AM
"Exponential backoff with jitter: retries in TypeScript" by Sascha Mirow-Stanitzok
#aws-lambda #serverless #amazon-sqs #amazon-dynamodb #typescript
#aws-lambda #serverless #amazon-sqs #amazon-dynamodb #typescript
A 429 from a PDF API usually means a monthly quota, not a transient blip — and exponential backoff on a quota error just retries uselessly for weeks. Check /api/usage before the batch runs, handle Retry-After for the rest →
A 429 from /api/fill-form, and what your retry loop should actually do
A quota 429 isn't a blip — backoff doesn't fix it, checking usage first does.
pdfops.dev
November 2, 2026 at 3:00 PM
A 429 from a PDF API usually means a monthly quota, not a transient blip — and exponential backoff on a quota error just retries uselessly for weeks. Check /api/usage before the batch runs, handle Retry-After for the rest →
Same in payments. The flows that survive production have idempotency keys, retries with backoff and a reconciliation job. The clever parts demo well, the boring parts stop money moving twice.
November 1, 2026 at 4:24 AM
Same in payments. The flows that survive production have idempotency keys, retries with backoff and a reconciliation job. The clever parts demo well, the boring parts stop money moving twice.
Webhooks failing silently in production? Learn how to build bulletproof webhook delivery with SQS, Lambda, and exponential backoff—covering the retry logic most engineers skip…
https://dev.to/sascha-ms/webhook-retries-reliable-delivery-with-sqs-and-lambda-3im5
#cloud #AWS
https://dev.to/sascha-ms/webhook-retries-reliable-delivery-with-sqs-and-lambda-3im5
#cloud #AWS
November 3, 2026 at 7:00 AM
Webhooks failing silently in production? Learn how to build bulletproof webhook delivery with SQS, Lambda, and exponential backoff—covering the retry logic most engineers skip…
https://dev.to/sascha-ms/webhook-retries-reliable-delivery-with-sqs-and-lambda-3im5
#cloud #AWS
https://dev.to/sascha-ms/webhook-retries-reliable-delivery-with-sqs-and-lambda-3im5
#cloud #AWS
A downstream service slowed down for ten seconds.
Every client retried at once with no backoff, and the wall of retries kept it down for an hour.
Retries without backoff turn a blip into an outage.
Back off exponentially, add jitter, cap the attempts.
Every client retried at once with no backoff, and the wall of retries kept it down for an hour.
Retries without backoff turn a blip into an outage.
Back off exponentially, add jitter, cap the attempts.
November 3, 2026 at 8:30 AM
A downstream service slowed down for ten seconds.
Every client retried at once with no backoff, and the wall of retries kept it down for an hour.
Retries without backoff turn a blip into an outage.
Back off exponentially, add jitter, cap the attempts.
Every client retried at once with no backoff, and the wall of retries kept it down for an hour.
Retries without backoff turn a blip into an outage.
Back off exponentially, add jitter, cap the attempts.
Does it handle rate-limit backoff gracefully when one provider dies mid-request, or does it just fail the batch?
November 3, 2026 at 1:37 AM
Does it handle rate-limit backoff gracefully when one provider dies mid-request, or does it just fail the batch?
Don't overwhelm APIs! Exponential backoff with randomized jitter is crucial for graceful retries, preventing system meltdown and ensuring stability. #devops
October 30, 2026 at 2:52 AM
Don't overwhelm APIs! Exponential backoff with randomized jitter is crucial for graceful retries, preventing system meltdown and ensuring stability. #devops
The retry loop with backoff is exactly what makes it dangerous. It looks like resilience. It is actually persistence of a hallucination. Tying completion to an observed outcome (idempotency key returned, state mutation confirmed, webhook received) is the only thing that converts "I trie...
November 1, 2026 at 9:38 PM
The retry loop with backoff is exactly what makes it dangerous. It looks like resilience. It is actually persistence of a hallucination. Tying completion to an observed outcome (idempotency key returned, state mutation confirmed, webhook received) is the only thing that converts "I trie...
313 of 333 endpoints answering with terms—that’s a solid pulse check. I’d put a retry with backoff on those 7 down ones before you trust the median.
November 3, 2026 at 3:54 AM
313 of 333 endpoints answering with terms—that’s a solid pulse check. I’d put a retry with backoff on those 7 down ones before you trust the median.
Throttling versus rate limiting changes how you respond to API limits. See how Retry-After, exponential backoff, and jitter make retries more reliable.
🔗 https://blog.n8n.io/throttling-vs-rate-limiting/
🔗 https://blog.n8n.io/throttling-vs-rate-limiting/
November 3, 2026 at 8:26 PM
Throttling versus rate limiting changes how you respond to API limits. See how Retry-After, exponential backoff, and jitter make retries more reliable.
🔗 https://blog.n8n.io/throttling-vs-rate-limiting/
🔗 https://blog.n8n.io/throttling-vs-rate-limiting/
Exponential backoff with randomized jitter is vital for API resilience, preventing a "thundering herd" from crushing services during outages. It's a simple, elegant pattern that makes your systems more robust and considerate. #devops ⚡
November 3, 2026 at 7:49 PM
Exponential backoff with randomized jitter is vital for API resilience, preventing a "thundering herd" from crushing services during outages. It's a simple, elegant pattern that makes your systems more robust and considerate. #devops ⚡
Exactly. Two more pieces: persist the operation ID before sending, so a lost response means a lookup, not a guess. And keep one retry owner, or browser, gateway and SDK retries multiply. Notes: yjtoon.yunusemrevurgun.com/blog/api-retries-with-backoff-and-idempotency
November 3, 2026 at 2:47 AM
Exactly. Two more pieces: persist the operation ID before sending, so a lost response means a lookup, not a guess. And keep one retry owner, or browser, gateway and SDK retries multiply. Notes: yjtoon.yunusemrevurgun.com/blog/api-retries-with-backoff-and-idempotency
Don't overwhelm APIs! Exponential backoff with randomized jitter is crucial for graceful retries, preventing system meltdown and ensuring stability. #devops
October 30, 2026 at 2:52 AM
Don't overwhelm APIs! Exponential backoff with randomized jitter is crucial for graceful retries, preventing system meltdown and ensuring stability. #devops
Outbox for multi-service steps: the business row and an intent record commit in one local transaction; a relay calls the external APIs with keys and backoff.
It closes one dual-write gap. The relay can still deliver twice, so consumers dedupe.
It closes one dual-write gap. The relay can still deliver twice, so consumers dedupe.
November 2, 2026 at 7:59 AM
Outbox for multi-service steps: the business row and an intent record commit in one local transaction; a relay calls the external APIs with keys and backoff.
It closes one dual-write gap. The relay can still deliver twice, so consumers dedupe.
It closes one dual-write gap. The relay can still deliver twice, so consumers dedupe.
- Good question ...
- Thankyou to my (equal) favourite Cartoonist / Satirist 'First Dog on the Moon' for another insightful offering
#BillionaireBullies #TooMuchPower #TooMuchAI #BackOff #BigTech #MakeLifeNormalAgain #RealWorld #SimplePleasures #Respect
- Thankyou to my (equal) favourite Cartoonist / Satirist 'First Dog on the Moon' for another insightful offering
#BillionaireBullies #TooMuchPower #TooMuchAI #BackOff #BigTech #MakeLifeNormalAgain #RealWorld #SimplePleasures #Respect
The internet is too awful so... fax machines are back! Yeah! woo www.theguardian.com/commentisfre...
Is the internet finally unusable? Time to go back to faxes and landlines | First Dog on the Moon
We embraced the internet and then forgot how to do things in the real world
www.theguardian.com
October 31, 2026 at 1:45 AM
- Good question ...
- Thankyou to my (equal) favourite Cartoonist / Satirist 'First Dog on the Moon' for another insightful offering
#BillionaireBullies #TooMuchPower #TooMuchAI #BackOff #BigTech #MakeLifeNormalAgain #RealWorld #SimplePleasures #Respect
- Thankyou to my (equal) favourite Cartoonist / Satirist 'First Dog on the Moon' for another insightful offering
#BillionaireBullies #TooMuchPower #TooMuchAI #BackOff #BigTech #MakeLifeNormalAgain #RealWorld #SimplePleasures #Respect
I have another idea.
Instead of fixing up these bases all around the world, how about closing many of them down.
It’s time to stop being an offensive military menace.
Let’s backoff from being an “imperialistic power”.
Military should be more for defensive purposes & to be collaborative with allies.
Instead of fixing up these bases all around the world, how about closing many of them down.
It’s time to stop being an offensive military menace.
Let’s backoff from being an “imperialistic power”.
Military should be more for defensive purposes & to be collaborative with allies.
November 3, 2026 at 10:21 PM
I have another idea.
Instead of fixing up these bases all around the world, how about closing many of them down.
It’s time to stop being an offensive military menace.
Let’s backoff from being an “imperialistic power”.
Military should be more for defensive purposes & to be collaborative with allies.
Instead of fixing up these bases all around the world, how about closing many of them down.
It’s time to stop being an offensive military menace.
Let’s backoff from being an “imperialistic power”.
Military should be more for defensive purposes & to be collaborative with allies.
2/4
• Queue & reconcile: accept actions locally, show a clear 'queued' state + ETA, assign reconcile_id, and retry with exponential backoff.
• Queue & reconcile: accept actions locally, show a clear 'queued' state + ETA, assign reconcile_id, and retry with exponential backoff.
October 29, 2026 at 8:37 PM
2/4
• Queue & reconcile: accept actions locally, show a clear 'queued' state + ETA, assign reconcile_id, and retry with exponential backoff.
• Queue & reconcile: accept actions locally, show a clear 'queued' state + ETA, assign reconcile_id, and retry with exponential backoff.
your app will lose signal. lifts, trains, car parks
what does the user see when they tap save?
- write locally first, show it as saved
- queue the request, retry with backoff
- add an idempotency key so retries never double post or charge
what does your app do offline?
#Flutter #MobileDev
what does the user see when they tap save?
- write locally first, show it as saved
- queue the request, retry with backoff
- add an idempotency key so retries never double post or charge
what does your app do offline?
#Flutter #MobileDev
November 3, 2026 at 8:38 AM
your app will lose signal. lifts, trains, car parks
what does the user see when they tap save?
- write locally first, show it as saved
- queue the request, retry with backoff
- add an idempotency key so retries never double post or charge
what does your app do offline?
#Flutter #MobileDev
what does the user see when they tap save?
- write locally first, show it as saved
- queue the request, retry with backoff
- add an idempotency key so retries never double post or charge
what does your app do offline?
#Flutter #MobileDev
The Anthropic SDK quits after 2 retries in ~1.2s; a mid-stream overloaded_error arrives as a 200. A retry layer for long runs.
https://startdebugging.net/2026/11/retry-and-backoff-for-long-agent-loops-under-overloaded-and-rate-limit-errors/?utm_source=bluesky&utm_medium=social&utm_campaign=auto
https://startdebugging.net/2026/11/retry-and-backoff-for-long-agent-loops-under-overloaded-and-rate-limit-errors/?utm_source=bluesky&utm_medium=social&utm_campaign=auto
November 1, 2026 at 10:14 AM
The Anthropic SDK quits after 2 retries in ~1.2s; a mid-stream overloaded_error arrives as a 200. A retry layer for long runs.
https://startdebugging.net/2026/11/retry-and-backoff-for-long-agent-loops-under-overloaded-and-rate-limit-errors/?utm_source=bluesky&utm_medium=social&utm_campaign=auto
https://startdebugging.net/2026/11/retry-and-backoff-for-long-agent-loops-under-overloaded-and-rate-limit-errors/?utm_source=bluesky&utm_medium=social&utm_campaign=auto
Exponential backoff with jitter helps prevent webhook retry stampedes, think of it like merging onto a busy highway, add some randomness to avoid collisions
October 29, 2026 at 6:06 PM
Exponential backoff with jitter helps prevent webhook retry stampedes, think of it like merging onto a busy highway, add some randomness to avoid collisions
CVE-2026-22114 - Missing brute-force protection for web interface
CVE ID : CVE-2026-22114
Published : Oct. 30, 2026, 11:17 a.m. | 12 minutes ago
Description : HTTP basic auth enforces no retry limit or backoff. Combined with the default service password, the keyspace is ...
CVE ID : CVE-2026-22114
Published : Oct. 30, 2026, 11:17 a.m. | 12 minutes ago
Description : HTTP basic auth enforces no retry limit or backoff. Combined with the default service password, the keyspace is ...
CVE-2026-22114 - Missing brute-force protection for web interface
HTTP basic auth enforces no retry limit or backoff. Combined with the default service password, the keyspace is exhaustible.
cvefeed.io
October 30, 2026 at 12:09 PM
CVE-2026-22114 - Missing brute-force protection for web interface
CVE ID : CVE-2026-22114
Published : Oct. 30, 2026, 11:17 a.m. | 12 minutes ago
Description : HTTP basic auth enforces no retry limit or backoff. Combined with the default service password, the keyspace is ...
CVE ID : CVE-2026-22114
Published : Oct. 30, 2026, 11:17 a.m. | 12 minutes ago
Description : HTTP basic auth enforces no retry limit or backoff. Combined with the default service password, the keyspace is ...
A good pipeline should fail loudly, early, and idempotently. Building retry loops without backoff or idempotency keys is just a DDOS attack against your own downstream endpoints.
October 30, 2026 at 12:38 AM
A good pipeline should fail loudly, early, and idempotently. Building retry loops without backoff or idempotency keys is just a DDOS attack against your own downstream endpoints.
"Test Step Functions with the TestState API" by Sascha Mirow-Stanitzok
#serverless #aws-step-functions #aws-lambda #aws-cdk #typescript
#serverless #aws-step-functions #aws-lambda #aws-cdk #typescript
Test Step Functions with the TestState API
Test Step Functions with the TestState API: check retry, backoff and catch with mocks in TypeScript, without a deployment and without an IAM role.
community.aws
October 31, 2026 at 6:30 PM
"Test Step Functions with the TestState API" by Sascha Mirow-Stanitzok
#serverless #aws-step-functions #aws-lambda #aws-cdk #typescript
#serverless #aws-step-functions #aws-lambda #aws-cdk #typescript
📦 cboxdk/laravel-webhooks v0.1.0
Cbox Webhooks: the outbound and inbound webhook engine for Laravel. A persistent outbox with per-endpoint sequencing, backoff with jitter, batching, a circuit breaker with auto-disable, a per-attem...
🔗 https://github.com/cboxdk/laravel-webhooks
Cbox Webhooks: the outbound and inbound webhook engine for Laravel. A persistent outbox with per-endpoint sequencing, backoff with jitter, batching, a circuit breaker with auto-disable, a per-attem...
🔗 https://github.com/cboxdk/laravel-webhooks
October 30, 2026 at 1:59 PM
📦 cboxdk/laravel-webhooks v0.1.0
Cbox Webhooks: the outbound and inbound webhook engine for Laravel. A persistent outbox with per-endpoint sequencing, backoff with jitter, batching, a circuit breaker with auto-disable, a per-attem...
🔗 https://github.com/cboxdk/laravel-webhooks
Cbox Webhooks: the outbound and inbound webhook engine for Laravel. A persistent outbox with per-endpoint sequencing, backoff with jitter, batching, a circuit breaker with auto-disable, a per-attem...
🔗 https://github.com/cboxdk/laravel-webhooks
2/3
• Runtime policy: on fee_spike or high-pending_rate, pause/deprioritize deferred tasks and increase backoff for retries.
• UI: show lightweight placeholders + a clear ETA for background settlement; never block the checkout path.
• Runtime policy: on fee_spike or high-pending_rate, pause/deprioritize deferred tasks and increase backoff for retries.
• UI: show lightweight placeholders + a clear ETA for background settlement; never block the checkout path.
October 29, 2026 at 8:47 PM
2/3
• Runtime policy: on fee_spike or high-pending_rate, pause/deprioritize deferred tasks and increase backoff for retries.
• UI: show lightweight placeholders + a clear ETA for background settlement; never block the checkout path.
• Runtime policy: on fee_spike or high-pending_rate, pause/deprioritize deferred tasks and increase backoff for retries.
• UI: show lightweight placeholders + a clear ETA for background settlement; never block the checkout path.