skills.rest
expanso-io
expanso-ioOFFICIAL
Explore all skills by this author →
GitHub

expanso-circuit-breakers

Implement circuit breaker fallbacks for resilient downstream service interactions.

1|Updated Feb 1, 2026
Search Tags:#error handling#data pipeline#resilience#circuit breaker#api gateway#fallback
One-click install
npx skills add https://github.com/expanso-io/expanso-skills --skill expanso-circuit-breakers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expanso-circuit-breakers
Source: https://github.com/expanso-io/expanso-skills/tree/main/skills/recipes/circuit-breakers
Command: npx skills add https://github.com/expanso-io/expanso-skills --skill expanso-circuit-breakers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures your data processing pipelines remain operational even when downstream services are unavailable by implementing a circuit breaker pattern with multiple fallback mechanisms.

Core Features & Use Cases

  • Resilient API Calls: Gracefully handles failures from primary and secondary APIs.
  • Data Fallback: Stores data locally or sends to a Kafka topic when primary destinations fail.
  • Use Case: An e-commerce order processing system needs to enrich order data with customer information from a primary API. If that API is down, the system can fall back to a secondary API, then to a local cache, and finally log the failed attempt to a dead-letter queue, ensuring no data is lost and the system remains responsive.

Quick Start

Run the circuit breaker pipeline with sample data using the provided shell script.

Frequently Asked Questions about expanso-circuit-breakers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does a circuit breaker pattern handle API failures in a data pipeline?▼

Yes, you can configure fallback logic to route data to a secondary service, persist it to local storage, or send it to a Kafka dead-letter topic, ensuring no data is lost during primary API downtime.

How do I implement resilient API calls with configurable timeouts and retries?▼

This approach fits data processing pipelines needing high resilience, supporting HTTP requests, Kafka outputs, and file-based persistence, making it suitable for e-commerce order systems or similar high-volume data flows.

What is the best way to prevent data loss when downstream services are unavailable?▼

If all primary and secondary API calls fail, the system persists data locally or logs the attempt to a dead-letter queue, allowing the pipeline to remain operational and recover the data later.

Does this circuit breaker approach work with Kafka and HTTP requests?▼

Limitations include dependency on the availability of secondary APIs or local storage capacity, and if the dead-letter queue is not monitored, data persistence can lead to delayed processing.

Related Skills

Explore More Software Engineering Skills→
smarmen86smarmen86

unfreeze

Deletes the freeze state file to restore write access across project directories.

Community
Basic
expanso-ioexpanso-io

expanso-enforce-schema

Validate incoming JSON data against a JSON schema and route invalid records to a dead-letter queue.

Official
Advanced
FaysilAlshareefFaysilAlshareef
4

polly-resilience

Compose Polly v8 resilience pipelines for HTTP and non-HTTP .NET operations.

Community
Advanced
jacexhjacexh

python-resilience

Implement automated retry and timeout logic for external Python calls.

Community
Advanced