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)

Shortage of skills and documentation

Legacy technologies (such as mainframes) have multiple complex components that depend on each other. These are extensive proprietary and costly servers that are not readily available if someone wants to develop skills on their own. It is challenging to retain application-development resources, and even more challenging to hire people with hands-on experience in old technology and operating systems.

Often, legacy systems are two or more decades older, and most of the workforce with those skills has retired. Also, these systems don't have the proper documentation to keep up the record of years of work. There are chances of significant knowledge loss as an older workforce rotates with a newer workforce. A lack of knowledge makes it riskier to change the system due to unknown dependencies. Any small feature requests are challenging to accommodate, due to system complexity and skill-set shortages.

New cutting-edge technologies such as big data, machine...