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

Dissecting regional failover

Up to this point we have covered all the building blocks for running serverless systems in multiple regions, including regional health checks, regional routing and data replication. Now let's see how all this comes together during a regional disruption.It is important to understand the various failure points and how the system should react as it fails over to a healthy region. Fortunately, our well-defined patterns provide us with a bounded set of function categories that we need to dissect. These are the query, command, trigger and listener functions we have across the patterns. We will use these to frame this topic.

Query failover

Data is essential to the operation of any application. Cached data, even if it is stale, is better than no data, provided the application is transparent with the users about the age of the data and the status of the system. So, when an application performs a query, we prefer to return stale data over no data or errors. Our...