CircuitBreakers

Stop calling a failing dependency temporarily to prevent cascading failure — closed/open/half-open states.

Why we need this / what value this brings

Stops a struggling dependency from being hammered by continued requests, giving it room to recover instead of making things worse.

When to use this

Once you have a dependency whose failure mode is 'slow and struggling' rather than 'instantly and cleanly down' — premature at Localz's current single-region, few-dependency scale.

How to use or implement this

Track failure rate per dependency; trip the breaker (fail fast) past a threshold, then periodically allow a test request through (half-open) to check recovery.

Research questions

• Would this matter yet for Localz's single-region, few-dependency setup, or is it premature?

---

Empty folder — drop notes, links, and findings here as you research.