Book Image

Software Architecture Patterns for Serverless Systems - Second Edition

By : John Gilbert
Book Image

Software Architecture Patterns for Serverless Systems - Second Edition

By: John Gilbert

Overview of this book

Organizations undergoing digital transformation rely on IT professionals to design systems to keep up with the rate of change while maintaining stability. With this edition, enriched with more real-world examples, you’ll be perfectly equipped to architect the future for unparalleled innovation. This book guides through the architectural patterns that power enterprise-grade software systems while exploring key architectural elements (such as events-driven microservices, and micro frontends) and learning how to implement anti-fragile systems. First, you'll divide up a system and define boundaries so that your teams can work autonomously and accelerate innovation. You'll cover the low-level event and data patterns that support the entire architecture while getting up and running with the different autonomous service design patterns. This edition is tailored with several new topics on security, observability, and multi-regional deployment. It focuses on best practices for security, reliability, testability, observability, and performance. You'll be exploring the methodologies of continuous experimentation, deployment, and delivery before delving into some final thoughts on how to start making progress. By the end of this book, you'll be able to architect your own event-driven, serverless systems that are ready to adapt and change.
Table of Contents (16 chapters)
Other Books You May Enjoy

Addressing intersystem differences

In Chapter 7, Bridging Intersystem Gaps, we covered the External Service Gateway (ESG) pattern. We deploy ESG services to multiple regions just like other autonomous services, but with one major difference. ESGs interact with external systems that may have different architectures with different regional approaches. The purpose of an ESG is to encapsulate these differences so that they do not corrupt the rest of the system. However, addressing these differences is a multi-dimensional problem that can make your head spin as you consider the challenges from all angles:

  • There is the perspective from your system and from the external system's.
  • Whether the flow is egress or ingress from your system's perspective.
  • Will your system be using a push or pull technique?
  • Is the regional disruption on your side or their side or both?
  • Is the external system in the same cloud, a different cloud or on-premises?
  • Is its topology primary/secondary or active/active...