The lighter let-it-crash is a circuit breaker. This is done quite frequently in the JVM world because .. well the JVM has a really shitty startup time.. even restarting threadpools can be expensive.<p>I get the whole let-it-crash but I really would like more tools on feedback control and backpressure handling (ie whats the right amount threads to allocate and how many failures&#x2F;timeouts should you allow etc...). Even monitoring is a pain (ie too many alarms). I don&#x27;t know if erlang provides libraries for this but its a hard problem (see <a href="https:&#x2F;&#x2F;github.com&#x2F;Netflix&#x2F;Hystrix&#x2F;issues&#x2F;131" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Netflix&#x2F;Hystrix&#x2F;issues&#x2F;131</a>).