Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Solutions Architect's Handbook
  • Toc
  • feedback
Solutions Architect's Handbook

Solutions Architect's Handbook

By : Saurabh Shrivastava, Neelanjali Srivastav
4.7 (59)
close
Solutions Architect's Handbook

Solutions Architect's Handbook

4.7 (59)
By: Saurabh Shrivastava, Neelanjali Srivastav

Overview of this book

Master the art of solution architecture and excel as a Solutions Architect with the Solutions Architect's Handbook. Authored by seasoned AWS technology leaders Saurabh Shrivastav and Neelanjali Srivastav, this book goes beyond traditional certification guides, offering in-depth insights and advanced techniques to meet the specific needs and challenges of solutions architects today. This edition introduces exciting new features that keep you at the forefront of this evolving field. Large language models, generative AI, and innovations in deep learning are cutting-edge advancements shaping the future of technology. Topics such as cloud-native architecture, data engineering architecture, cloud optimization, mainframe modernization, and building cost-efficient and secure architectures remain important in today's landscape. This book provides coverage of these emerging and key technologies and walks you through solution architecture design from key principles, providing you with the knowledge you need to succeed as a Solutions Architect. It will also level up your soft skills, providing career-accelerating techniques to help you get ahead. Unlock the potential of cutting-edge technologies, gain practical insights from real-world scenarios, and enhance your solution architecture skills with the Solutions Architect's Handbook.
Table of Contents (20 chapters)
close
18
Other Books You May Enjoy
19
Index

Think loose coupling

A traditional application is deployed on a tightly integrated server fleet where each server has a specific responsibility. Often, applications depend on multiple servers for completeness of functionality.

As shown in the following diagram, in a tightly coupled architecture, the web server fleet has a direct dependency on all application servers, and vice versa:

Figure 2.7: Tightly coupled architecture

In the preceding architecture diagram, if one application server goes down, then all web servers will start receiving errors, as the request will route to an unhealthy application server, which may cause a complete system failure. With tightly coupled architecture, if you want to scale by adding and removing servers, it requires lots of work, as all connections need to be set up appropriately.

With loose coupling, you can add an intermediate layer, such as a load balancer or a queue, which automatically handles failures or scaling for you.

...
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete