Book Image

AWS for Solutions Architects

By : Alberto Artasanchez
3 (1)
Book Image

AWS for Solutions Architects

3 (1)
By: Alberto Artasanchez

Overview of this book

One of the most popular cloud platforms in the world, Amazon Web Services (AWS) offers hundreds of services with thousands of features to help you build scalable cloud solutions; however, it can be overwhelming to navigate the vast number of services and decide which ones best suit your requirements. Whether you are an application architect, enterprise architect, developer, or operations engineer, this book will take you through AWS architectural patterns and guide you in selecting the most appropriate services for your projects. AWS for Solutions Architects is a comprehensive guide that covers the essential concepts that you need to know for designing well-architected AWS solutions that solve the challenges organizations face daily. You'll get to grips with AWS architectural principles and patterns by implementing best practices and recommended techniques for real-world use cases. The book will show you how to enhance operational efficiency, security, reliability, performance, and cost-effectiveness using real-world examples. By the end of this AWS book, you'll have gained a clear understanding of how to design AWS architectures using the most appropriate services to meet your organization's technological and business requirements.
Table of Contents (20 chapters)
1
Section 1: Exploring AWS
4
Section 2: AWS Service Offerings and Use Cases
11
Section 3: Applying Architectural Patterns and Reference Architectures
17
Section 4: Hands-On Labs

Understanding the asynchronous communication service

An essential component of a microservice architecture is the ability of the components to communicate asynchronously. Some of the components are going to produce data that then needs to be consumed by other components.

Having a centralized area where the communication can take place might be the single most important decision to keep the architecture simple. If we allow services to communicate among each other, the combinatorial explosion of those connections and the complexity that will result from it will soon bury us and doom the project. The following figure illustrates how many more connections are needed if we don't have a centralized communication mechanism:

Figure 14.4 – Point-to-point architecture versus event bus architecture

On the left of the figure where the point-to-point architecture is illustrated, there are many more connections that need to be made if an event bus is not...