Resilience and control

Resilience and control patterns protect a route from failure, limit throughput, and scope error handling. They map to the System Management family in Hohpe and Woolf, adapted to the Tower middleware pipeline.

• Circuit Breaker — trip after repeated failures and recover after a cool-down
• Do Try — scoped catch and finally blocks around a group of steps
• Throttler — cap the rate of exchanges through a route
• Idempotent Consumer — reject duplicates by correlation key
• Delayer — hold an exchange for a fixed duration
• Loop — repeat a sub-route a fixed number of times
• Validator — check exchange content against a schema

For the error-handling contract that governs catch and finally behavior, see error handling.