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)

Defining a strategy for system modernization

Often, a legacy system gets left out of an overall enterprise digital strategy, and issues get addressed on a need basis. Taking a reactive approach holds back organizations from executing overall system modernization and benefits.

If your legacy system has serious business challenges such as security and compliance issues or is unable to address the business need, you can take a big-bang approach. In the big-bang method, you can build a new system from scratch and shut down the old system. This approach has more risk but addresses a business need that can be mitigated from the existing legacy system.

The other approach you can take is a phased approach, where you upgrade one module at a time and keep running both old and new systems. A phased approach has less risk but takes a long time and may be more expensive as you need to maintain both environments, with additional network and infrastructure bandwidth.

Taking any of these approaches...