Resilient Architecture Simplified - Isabel Palomar - @javaMexico

Resilient Architecture Simplified

In this talk, you will learn about some of the concepts frequently used when designing mission-critical applications, some of the concepts are Resilience, Disaster Recovery, High Availability, and Fault Tolerance. I will walk you through some of the examples, as well as present you some of the libraries/integrations that can be used for JVM systems.

Transcript

1. Here is where your presentation begins Resilient Architecture Simplified Next Back Start Table of contents
2. Here is where your presentation begins Resilient Architecture Simplified Next Back Start Table of contents
3. Who am I ? ISABEL PALOMAR - Staff Software Engineer with random hobbies - 12 years of experience - I was born in Cd. Guzman, Jalisco Back Start Table of contents Next
4. 02 01 What? Table of contents Next Back Start Table of contents Why? 03 Core Concepts 05 Resources 04 Conclusions
5. 01 What is a resilient architecture? Next Back Start Table of contents What? 🤔
6. Let’s talk about systems Next Back Start Table of contents
7. At the end of the day… Next Back Start Table of contents
8. At the end of the day… Next Back Start Table of contents
9. The normal state of operation is PARTIAL FAILURE Back Start Table of contents Partial FAILURE Next
10. The normal state of operation is PARTIAL FAILURE Back Start Table of contents Partial FAILURE Next Etc, etc….
11. 02 Why is important? Next Back Start Table of contents Why? 󰤆
12. Failure might be critical For some applications failure might not be life critical, but it can result in lost revenue and this is why we need to build resilience architecture Next Back Start Table of contents
13. Yes, there is a cost Next Back Start Table of contents Revenue Loss Resiliency Cost ⚖
14. Is not only about Software… It starts at the infrastructure level progresses to network, data and influences your application design Next Back Start Table of contents Build a resilient architecture is not only about software.
15. 03 The concepts you need to know Next Back Start Table of contents CORE CONCEPTS
16. 4 Core Concepts Resiliency Disaster Recovery High Availability Fault Tolerance Next Back Start Table of contents
17. 4 Core Concepts RESILIENCY Disaster Recovery High Availability Fault Tolerance Next Back Start Table of contents
18. Resiliency Ability for a system to handle and eventually recover from unexpected conditions Next Back Start Table of contents
19. 4 Core Concepts Resiliency DISASTER RECOVERY High Availability Fault Tolerance Next Back Start Table of contents
20. Disaster Event that prevents your systems from fulfilling its business objectives. Next Back Start Table of contents
21. Nature of a disaster Next Back Start Table of contents Technical failure Natural Disaster Human actions
22. Geographical impact Next Back Start Table of contents COUNTRY WIDE GLOBAL LOCAL
23. Disaster Recovery Strategy Next Back Start Table of contents Both, nature of the disaster and the geographical impact are important considerations to create a: Disaster Recovery Strategy
24. Amount of impact a business can take during a disaster Back Start Table of contents Disaster RECOVERY Next
25. BCP (Business Continuity Plan) Set of actions a company puts into motion when disaster strikes. ---- The primary objective of DR is Business Continuity Next Back Start Table of contents
26. 4 Core Concepts Resiliency Disaster Recovery HIGH AVAILABILITY Fault Tolerance Next Back Start Table of contents
27. High Availability Next Back Start Table of contents Refers to a system that is designed to avoid loss of service by reducing or managing failures and minimizing planned downtime. Elimination of single points of failure. Reliable crossover. Detection of failures as they occur.
28. A High available system needs REDUNDANCY Next Back Start Table of contents MONITORING MECHANISM FOR FAILOVER OR FALLBACK Availability Zone 1 Availability Zone 2
29. HA != 100% - HA 99.999 (Five 9s) Next Back Start Table of contents https://en.wikipedia.org/wiki/High_availability#Percentage_calculation
30. 4 Core Concepts Resiliency Disaster Recovery HIGH AVAILABILITY FAULT TOLERANCE Next Back Start Table of contents
31. Fault tolerance Next Back Start Table of contents Fault tolerance refers to the ability of a system (computer, network, cloud cluster, etc.) to continue operating without interruption when one or more of its components fail.
32. Example of Fault tolerance - Applications running in parallel mirroring each other require SYNCHRONIZATION And hence… COST MODE Next Back Start Table of contents
33. Failure Next Back Start Table of contents Hard Disk Failures Network Issues Power Problems And so on… Fault tolerance systems are build for failure
34. While both fault tolerance and high availability refer to a system’s functionality over time, there are differences that highlight their individual importance in your business continuity planning. Back Start Table of contents Fault Tolerance vs High Availability Next
35. Fault Tolerance vs High Availability Next Back Start Table of contents TWIN ENGINE JET CAR WITH SPARE TIRE A twin-engine airplane is a fault tolerant system – if one engine fails, the other one kicks in, allowing the plane to continue flying. Conversely, a car with a spare tire is highly available. A flat tire will cause the car to stop, but downtime is minimal because the tire can be easily replaced No downtime Minimized Downtime
36. Netflix Hystrix (2012) 󰘬 Back Start Table of contents Resiliency in Software Next Resilience4j Failsafe - CircuitBreaker - Bulkhead - RateLimiter - Retry - TimeLimiter - Cache - Fallback
37. Back Start Table of contents Example Circuit Breaker Next Resilience4j The state of the CircuitBreaker changes from CLOSED to OPEN when the failure rate is equal or greater than a configurable threshold. For example when more than 50% of the recorded calls have failed.
38. Back Start Table of contents Example Circuit Breaker Next service.resilience4j.circuitbreaker.state
39. 04 The things you need to remember Next Back Start Table of contents CONCLUSIONS
40. FAILURES ARE NORMAL Next Back Start Table of contents In brief
41. Next Back Start Table of contents — WERNER VOGELS, CTO, AMAZON “Failures are a given and everything will eventually fail over time: from routers to hard disks, from operating systems to memory units corrupting TCP packets, from transient errors to permanent failures. This is a given, whether you are using the highest quality hardware or lowest cost components.”
42. 05 Articles/videos you need to read/watch Next Back Start Table of contents Resources
43. Additional resources - Patterns for Resilient Architecture - Adrian Hornsby - https://www.youtube.com/watch?v=gET51_C3k5s - 10 lessons from 10 Years at AWS - https://www.allthingsdistributed.com/2016/03/10-lessons-from-10-years-of-aws.html - RPO and RTO targets for cloud - https://aws.amazon.com/blogs/mt/establishing-rpo-and-rto-targets-for-cloud-applications/ - High availability vs Fault Tolerance - https://www.youtube.com/watch?v=miEHdzqlRsY - Fault tolerance - https://www.imperva.com/learn/availability/fault-tolerance/ Next Back Start Table of contents
44. CREDITS: This presentation template was created by Slidesgo, and includes icons by Flaticon, and infographics & images by Freepik Thanks! @IsabelPalomar Next Back Start Table of contents