Architectural resiliency
Regardless of the techniques used to make an enterprise solution highly available (HA), failure at some point is inevitable. Resiliency is how fast a system reacts and then recovers to such failures. Jeremy Deane covers a number of techniques and patterns for addressing architectural resiliency, including intelligent agents, tolerant reader, and circuit breaker.
| Talk Title | Architectural resiliency |
| Speakers | Jeremy Deane (Foundation Medicine) |
| Conference | O’Reilly Software Architecture Conference |
| Conf Tag | Engineering the Future of Software |
| Location | New York, New York |
| Date | April 3-5, 2017 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Failure of highly available (HA) enterprise solutions is inevitable. But in today’s highly interconnected global economy, uptime is critical. The impact of downtime is magnified when factoring in service level agreement (SLA) penalties and lost revenue. Even more harmful is the damage to an organization’s reputation as angry customers vent their frustrations on social media. Resiliency, the neglected stepchild of availability, is often an afterthought. Yet an enterprise solution without resiliency is not truly HA. Jeremy Deane covers a number of techniques and patterns for addressing architectural resiliency, including intelligent agents, tolerant reader, and circuit breaker. Applying these techniques to an enterprise solution will increase mean time to failure (MTTF), aka fault tolerance, and decrease mean time to recovery (MTTR).
