Book Image

Solutions Architect's Handbook - Second Edition

By : Saurabh Shrivastava, Neelanjali Srivastav
4 (2)
Book Image

Solutions Architect's Handbook - Second Edition

4 (2)
By: Saurabh Shrivastava, Neelanjali Srivastav

Overview of this book

Becoming a solutions architect requires a hands-on approach, and this edition of the Solutions Architect's Handbook brings exactly that. This handbook will teach you how to create robust, scalable, and fault-tolerant solutions and next-generation architecture designs in a cloud environment. It will also help you build effective product strategies for your business and implement them from start to finish. This new edition features additional chapters on disruptive technologies, such as Internet of Things (IoT), quantum computing, data engineering, and machine learning. It also includes updated discussions on cloud-native architecture, blockchain data storage, and mainframe modernization with public cloud. The Solutions Architect's Handbook provides an understanding of solution architecture and how it fits into an agile enterprise environment. It will take you through the journey of solution architecture design by providing detailed knowledge of design pillars, advanced design patterns, anti-patterns, and the cloud-native aspects of modern software design. By the end of this handbook, you'll have learned the techniques needed to create efficient architecture designs that meet your business requirements.

Related Content you might be interested in

Current Title:

Small book image
Solutions Architect's Handbook - Second Edition
Saurabh Shrivastava | Neelanjali Srivastav
Jan, 2022 | 590 pages
Small book image
AWS for Solutions Architects
Neelanjali Srivastav | Alberto Artasanchez | Imtiaz Sayed | Saurabh Shrivastava
Apr, 2023 | 692 pages
Small book image
Optimizing Your Modernization Journey with AWS
Mridula Grandhi
Jul, 2023 | 418 pages
Small book image
Cloud Native Architectures
Erik Farr | Tom Laszewski | Piyum Zonooz | Kamal Arora
Aug, 2018 | 358 pages
Table of Contents (22 chapters)
Preface
Preface
Who this book is for?
What this book covers
To get the most out of this book
Get in touch
Free Chapter
1
The Meaning of Solution Architecture
The Meaning of Solution Architecture
What is solution architecture?
The evolution of solution architecture
Why is solution architecture important?
The benefits of solution architecture
Solution architecture in the public cloud
Summary
2
Solution Architects in an Organization
Solution Architects in an Organization
Types of roles for a solution architect
Understanding a solution architect's responsibilities
Solution architects in an agile organization
Summary
3
Attributes of the Solution Architecture
Attributes of the Solution Architecture
Scalability and elasticity
Scaling your architecture
Static content scaling
High availability and resiliency
Fault tolerance and redundancy
Disaster recovery and business continuity
Extensibility and reusability
Usability and accessibility
Portability and interoperability
Operational excellence and maintainability
Security and compliance
Cost optimization and budget
Summary
4
Principles of Solution Architecture Design
Principles of Solution Architecture Design
Scaling workloads
Building a resilient architecture
Design for performance
Using replaceable resources
Think loose coupling
Think service not server
Using the right storage for the right requirements
Think data-driven design
Overcoming architectural constraints
Taking the minimum viable product approach
Adding security everywhere
Applying automation everywhere
Summary
5
Cloud Migration and Hybrid Cloud Architecture Design
Cloud Migration and Hybrid Cloud Architecture Design
Benefits of cloud native architecture
Popular public cloud choices
Creating a cloud migration strategy
Choosing a cloud strategy
Steps for cloud migration
Creating hybrid cloud architecture
Taking a multi-cloud approach
Designing cloud native architecture
Summary
Further reading
6
Solution Architecture Design Patterns
Solution Architecture Design Patterns
Building an n-tier layered architecture
Creating a multi-tenant SaaS-based architecture
Building stateless and stateful architecture designs
Understanding service-oriented architecture
Building a serverless architecture
Creating a microservice architecture
Building a queue-based architecture
Creating an event-driven architecture
Building a cache-based architecture
Understanding the circuit breaker pattern
Implementing the bulkheads pattern
Creating a floating IP pattern
Deploying an application with a container
Database handling in application architecture
Avoiding anti-patterns in solution architecture
Summary
7
Performance Considerations
Performance Considerations
Design principles for architecture performance
Technology selection for performance optimization
Managing performance monitoring
Summary
8
Security Considerations
Security Considerations
Designing principles for architectural security
Selecting technology for architectural security
Security and compliance certifications
The cloud's shared security responsibility model
Summary
9
Architectural Reliability Considerations
Architectural Reliability Considerations
Design principles for architectural reliability
Technology selection for architectural reliability
Improving reliability with the cloud
Summary
10
Operational Excellence Considerations
Operational Excellence Considerations
Designing principles for operational excellence
Selecting technologies for operational excellence
Achieving operational excellence in the public cloud
Summary
11
Cost Considerations
Cost Considerations
Design principles for cost optimization
Techniques for cost optimization
Cost optimization in the public cloud
Summary
12
DevOps and Solution Architecture Framework
DevOps and Solution Architecture Framework
Introducing DevOps
Understanding the benefits of DevOps
Understanding the components of DevOps
Introducing DevSecOps
Combining DevSecOps and CI/CD
Implementing a CD strategy
Implementing continuous testing in the CI/CD pipeline
Using DevOps tools for CI/CD
Implementing DevOps best practices
Building DevOps and DevSecOps in the cloud
Summary
13
Data Engineering for Solution Architecture
Data Engineering for Solution Architecture
What is big data architecture?
Designing big data processing pipelines
Data ingestion
Storing data
Processing data and performing analytics
Visualizing data
Designing big data architectures
Big data architecture best practices
Summary
14
Machine Learning Architecture
Machine Learning Architecture
What is machine learning?
Working with data science and ML
Machine learning in the cloud
Building machine learning architecture
Machine learning reference architecture
Machine learning operations
Deep learning
Summary
15
The Internet of Things Architecture
The Internet of Things Architecture
What is the Internet of Things?
Components of IoT architecture
IoT in the cloud
Building an industrial IoT solution
Summary
16
Quantum Computing
Quantum Computing
The building blocks of quantum computers
The working mechanism of quantum computers
Types of quantum computers
Quantum computing in real life
Quantum computing in the cloud
Summary
17
Rearchitecting Legacy Systems
Rearchitecting Legacy Systems
Learning the challenges of legacy systems
Benefits of system modernization
Defining a strategy for system modernization
Looking at legacy system modernization techniques
Defining a cloud migration strategy for legacy systems
Mainframe migration with the public cloud
Summary
18
Solution Architecture Document
Solution Architecture Document
Purpose of the SAD
Views of the SAD
Structure of the SAD
IT procurement documentation for a solution architecture
Summary
19
Learning Soft Skills to Become a Better Solution Architect
Learning Soft Skills to Become a Better Solution Architect
Acquiring pre-sales skills
Presenting to C-level executives
Taking ownership and accountability
Defining strategy execution with objectives and key results
Thinking big
Being flexible and adaptable
Design thinking
Being a builder by engaging in coding hands-on
Becoming better with continuous learning
Being a mentor to others
Becoming a technology evangelist and thought leader
Summary
20
Other Books You May Enjoy
Other Books You May Enjoy
21
Index
Index

The evolution of solution architecture

Solution architecture has evolved with technological modernization. Today, solution architecture design has changed drastically compared to a couple of decades ago, due to the increasing use of the internet, the availability of high-bandwidth networks, the low cost of storage, and compute availability.

Back in the days before the era of the internet, most solution designs focused on providing a thick desktop client that was capable of operating with low bandwidth and working offline when a system could not connect to the internet.

This technology has evolved over the two decades. Service-oriented architecture (SOA) started taking shape for distributed design, and applications started moving from monolithic to modern n-tier architecture, where the frontend server, application server, and database were live in their own compute and the storage layer. These SOAs are mostly achieved by an XML-based messaging protocol, called Simple Object Access Protocol (SOAP). A major component of this is its ability to follow a client-server model in order to create services.

In this age of digitization, you will see microservice-based solution design becoming increasingly popular, which is based on JavaScript Object Notation (JSON) messaging and the Representational State Transfer (REST) service. These are web APIs, which do not require XML-based web service protocols (SOAPs) to support their interfaces. They rely on web-based HTTP protocols such as POST, GET, UPDATE, DELETE, and so on. You will learn more about different architecture patterns in great detail in Chapter 6, Solution Architecture Design Patterns.

The microservice architecture addresses the need for changing requirements in an agile environment, where any solution changes need to be accommodated and deployed rapidly. Organizations have to be agile to stay ahead of the competition, which forces solution architecture to be flexible compared to the waterfall model, where you have a long cycle before project release.

The web-based microservice architecture is fueled by an almost unlimited resource capability, which is available from cloud providers, and can scale in minutes or seconds. It's becoming easier to innovate, experiment, and change as solution architects and developers can risk failing without impacting business functions.

Previous Section
End of Section 3
Next Section