Resilient Cloud Architecture Design Patterns

Resilient architecture is fundamental when working in distributed, cloud-based systems. Designing and architecting large-scale applications managing millions of requests brings unique challenges with availability, performance, and integration. You will need to make difficult choices and evaluate tradeoffs. Luckily, you can use different architecture patterns to make a distributed application more resilient. Based on evolutionary architecture, this approach enables you to create systems designed to evolve with the ever-changing software development ecosystem. Resilient architecture patterns will allow you to create systems that continue functioning even when components fail.

Join expert Rohit Bhardwaj to learn how to implement an evolutionary architecture approach and understand resilient architecture patterns. This training will explore architecture decisions you may need to make when evaluating your architecture to improve performance and resiliency. For example, you will no longer struggle to handle millions of requests per second or face issues when routing traffic.
What you'll learn — and how you can apply it

By the end of this live, hands-on, online course, you'll understand the following:
How to create responsive, maintainable, extensible architecture from resilient, elastic design utilizing message-driven services

How to design cost-effective Recovery Point Objectives (RPOs) and Recovery Time Objectives (RTOs)

How to identify blocking issues with microservices in the cloud

How to evaluate caching strategies that can help lower costs and protect from DOS attacks

And you'll be able to:

Design high availability, high scalability, low latency, and resilient architectures.

Analyze and review implementations.

Identify key scalability challenges in your company.

Prevent cascading failures and preserve functionality.

This training is for you because…

You have an existing need to evaluate your current architecture.

You want to understand best practices.

You need to design new systems and want to evaluate which pattern to use.

Prerequisites

Basic knowledge of software architecture

Familiarity with design principles

Thinking application as stateless for all the API calls makes the system available most of the time and requires creating a cache for common distributed data. Next, we examine how to deal with cascading failures and timeout scenarios. As part of auto-healing, applications need to Detect, Prevent, Recover, Mitigate, and Complement so that the service is resilient.

The key takeaways for the audience are as follows:

*Resiliency is essential for any feature in the cloud.

*Understanding the value chain is critical to identifying failure points.

*Challenges come in determining if there is a failure and designing the system for auto-
healing

*The focus should be first to prevent a failure from occurring.

*Identifying critical challenges in your company and tools and techniques to auto-heal and provide a sustainable solution

Course Schedule

Evolutionary Architecture:

– Scaling to 100 million customers

– Understanding Requirements - Empathy Map

– Fail Points

– Defining KPIs

Resilient Patterns:

– BulkHead pattern

– Routing Strategies

– Design Issues with Microservices

– API Gateway Pattern

– Database per Service Pattern

– Database Sharding Patterns

– Fan out Pattern

– Publish-Subscribe Pattern

– Command Query Responsibility Segregation (CQRS)

– Message filter pattern

– Topic-queue-chaining Pattern

– Message Partitioning Patterns

– Priority Queue Pattern

Caching:

– Caching and Failure Injection

– Distributed system challenges

– Caching Patterns

– Order in Chaos

– Resilient Steps

– Resources