Developer builds Node.js resilience library 'Breakwater' to fix policy composition gaps

A developer published an open-source Node.js library called Breakwater after finding that existing resilience tools like opossum and cockatiel lack unified policy composition, observability, and clear documentation of ordering consequences. The core problem identified is that nesting retry, circuit breaker, timeout, and fallback policies in different orders produces fundamentally different system behaviors, a distinction most libraries never explain. Breakwater enforces a deliberate, documented default policy order — fallback wrapping retry, rate limit, bulkhead, circuit breaker, and timeout from outside in — so each layer guards the right concern. For teams needing custom ordering, the library also exposes a compose() function that makes policy nesting explicit and readable. The library is available on npm under the package name 'breakwater' and targets Node.js projects that have historically bolted on resilience logic piecemeal after outages.