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)

Applying best practices for disaster recovery

As you start thinking about disaster recovery, here are some important considerations:

  • Start small and build as needed: Make sure to streamline the first step of taking a backup. Most of the time, organizations lose data as they didn't have an efficient backup strategy. Take a backup of everything, whether it is your file server, machine image, or databases.

Keeping lots of active backups could increase costs, so make sure to apply a life cycle policy to archive and delete data as per business needs. For example, you can choose to keep a 90-day active backup and after that store that in low-cost archive storage such as a tape drive or Amazon Glacier. After 1 or 2 years, you may want to set a lifecycle policy to delete the data. Compliance such as PCI-DSS may require users to store data for 7 years, and in that case, you must choose archival data storage to reduce costs.

  • Check your software licenses: Managing software licenses can...