https://bravenewgeek.com/tag/resilience-engineering/Recent content in Resilience Engineering on Brave New GeekHugoen-usFri, 23 Dec 2016 12:05:50 -0600https://bravenewgeek.com/take-it-to-the-limit-considerations-for-building-reliable-systems/Tue, 20 Dec 2016 19:55:52 -0600https://bravenewgeek.com/take-it-to-the-limit-considerations-for-building-reliable-systems/<p>Complex systems usually operate in failure mode. This is because a complex system typically consists of many discrete pieces, each of which can fail in isolation (or in concert). In a microservice architecture where a given function potentially comprises several independent service calls, <em>high</em> availability hinges on the ability to be <em>partially</em> available. This is a core tenet behind resilience engineering. If a function depends on three services, each with a reliability of 90%, 95%, and 99%, respectively, partial availability could be the difference between 99.995% reliability and 84% reliability (assuming failures are independent). Resilience engineering means designing with failure as the normal.</p>https://bravenewgeek.com/designed-to-fail/Tue, 21 Jul 2015 20:17:17 -0500https://bravenewgeek.com/designed-to-fail/<p>When it comes to reliability engineering, people often talk about things like fault injection, monitoring, and operations runbooks. These are all critical pieces for building systems which can withstand failure, but what’s less talked about is the need to design systems which <em>deliberately</em> fail.</p> <p>Reliability design has a natural progression which closely follows that of architectural design. With monolithic systems, we care more about preventing failure from occurring. With service-oriented architectures, controlling failure becomes less manageable, so instead we learn to anticipate it. With highly distributed microservice architectures where failure is all but guaranteed, we <em>embrace</em> it.</p>