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)

Warm standby

Warm standby, also known as fully working low capacity standby, is like the next level of the pilot light. It is the option where you use the agility of the cloud to provide low-cost DR. It increases the cost but also allows data to recover more quickly by having a small subset of services already running.

You can decide whether your disaster recovery environment should be enough to accommodate 30% or 50% of production traffic. Alternatively, you can also use this for non-production testing.

As shown in the following diagram, in the warm standby method, two systems are running—the central system and a low-capacity system—on a cloud such as AWS. You can use a router such as Amazon Route 53 to distribute requests between the central system and the cloud system:

Warm standby scenario running an active-active workload with a low capacity

When it comes to a database, warm standby has a similar approach to pilot light, where data is continuously replicating from...