Book Image

Solutions Architect's Handbook

By : Saurabh Shrivastava, Neelanjali Srivastav
Book Image

Solutions Architect's Handbook

By: Saurabh Shrivastava, Neelanjali Srivastav

Overview of this book

Becoming a solutions architect gives you the flexibility to work with cutting-edge technologies and define product strategies. This handbook takes you through the essential concepts, design principles and patterns, architectural considerations, and all the latest technology that you need to know to become a successful solutions architect. This book starts with a quick introduction to the fundamentals of solution architecture design principles and attributes that will assist you in understanding how solution architecture benefits software projects across enterprises. You'll learn what a cloud migration and application modernization framework looks like, and will use microservices, event-driven, cache-based, and serverless patterns to design robust architectures. You'll then explore the main pillars of architecture design, including performance, scalability, cost optimization, security, operational excellence, and DevOps. Additionally, you'll also learn advanced concepts relating to big data, machine learning, and the Internet of Things (IoT). Finally, you'll get to grips with the documentation of architecture design and the soft skills that are necessary to become a better solutions architect. By the end of this book, you'll have learned techniques to create an efficient architecture design that meets your business requirements.
Table of Contents (18 chapters)

Multi-site

Lastly, the multi-site strategy, also known as hot standby, helps you to achieve near-zero RTO and RPO. In multi-site, your disaster recovery site is an exact replica of the primary site with continuous data replication and traffic flow. It is known as multi-site architecture due to the automated load balancing of traffic across regions or between on premise and the cloud.

As shown in the following diagram, multi-site is the next level of disaster recovery to have a fully functional system running in the cloud at the same time as on-premises systems:

Multi-site scenario running an active-active workload with a full capacity

The advantage of the multi-site approach is that it is ready to take a full production load at any moment. It's similar to warm standby but running full capacity in the disaster recovery site. If the primary site goes down, all traffic can be immediately failed over to the disaster recovery site.

A multi-site disaster recovery pattern is most expensive...