Is the retry logic customizable?

Yes, you can configure the maximum number of retries, the base delay, the maximum delay, and specify exactly which HTTP status codes or error types should trigger a retry.

How does the circuit breaker prevent system failure?

The circuit breaker monitors for a high frequency of failures; once a threshold is reached, it 'opens' to block further requests, giving the external service time to recover and preventing your application from wasting resources.

Can I use this for TypeScript projects?

Yes, all patterns are implemented with TypeScript interfaces and classes, providing type-safe solutions for robust API development.

What resilience patterns are included in this skill?

This skill provides patterns for exponential backoff retries, circuit breakers, request deduplication, token-bucket rate limiting, and batch queuing.

API Resilience & Rate Limiting

Name: API Resilience & Rate Limiting
Author: Naw3

byNaw3

API Development

Implements robust API integration patterns including retries, circuit breakers, and rate limiting to ensure system stability.

About

This skill provides a comprehensive suite of resilience patterns designed to handle the complexities of modern web integrations. It offers production-ready implementations for exponential backoff retries, stateful circuit breakers to prevent cascading failures, request deduplication for bandwidth efficiency, and token-bucket rate limiting. By incorporating these patterns, developers can build fault-tolerant applications that gracefully handle third-party service outages, network instability, and strict API rate constraints, ensuring a seamless user experience even when external dependencies fail.

Key Features

Request deduplication and TTL caching to reduce redundant network overhead.
Batch request queuing to efficiently manage high-volume API interactions.
Token-bucket rate limiting for precise control over outgoing request velocity.
Exponential backoff with jitter to prevent 'thundering herd' issues during retries.
Stateful Circuit Breaker pattern to stop requests to failing downstream services.
0 GitHub stars

Use Cases

Managing strict API quotas and avoiding 429 'Too Many Requests' errors.
Integrating unreliable third-party REST/GraphQL APIs that require graceful error handling.
Building resilient microservices that must remain responsive during partial system outages.

About

Key Features

Request deduplication and TTL caching to reduce redundant network overhead.
Batch request queuing to efficiently manage high-volume API interactions.
Token-bucket rate limiting for precise control over outgoing request velocity.
Exponential backoff with jitter to prevent 'thundering herd' issues during retries.
Stateful Circuit Breaker pattern to stop requests to failing downstream services.
0 GitHub stars

Use Cases

Managing strict API quotas and avoiding 429 'Too Many Requests' errors.
Integrating unreliable third-party REST/GraphQL APIs that require graceful error handling.
Building resilient microservices that must remain responsive during partial system outages.