When we discussed resiliency in Chapter 10, we mentioned how this means the self-healing abilities of your solution. Designing for resiliency means building a solution that can and will recover from errors and that will complete its tasks successfully even if there are issues in the infrastructure or in the data.
Resiliency, however, does not mean that you will not need to monitor your solution closely. Even if your solution ...
Get Pro Serverless Data Handling with Microsoft Azure: Architecting ETL and Data-Driven Applications in the Cloud now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
Get Mark Richards’s Software Architecture Patterns ebook to better understand how to design components—and how they should interact.
Dive in for free with a 10-day trial of the O’Reilly learning platform—then explore all the other resources our members count on to build skills and solve problems every day.
Start your free trial Become a member now