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

Choosing a regional topology

The terminology for regional topology is pretty cut and dry, but when we get down into the weeds it is common to find lots of variations in the overall interpretations and implementation details. In the context of serverless systems, we have two main options, primary/secondary and active/active, with some variations. Let's look at these in the order we might adopt them.

Primary / Hot-Secondary

Primary/Secondary is the most common regional topology for traditional systems. We route users to the primary region (east) and we failover to the secondary region (west). The failover process usually involves manual intervention, so it is more correct to call this a Primary/Cold-Secondary topology.For our serverless systems, we employee a Primary/Hot-Secondary topology. We are deploying all our services in both regions, and they are ready to go, because we are replicating the data in near real time, as we will see in the Replicating across regions section. We...