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

Preparing for regional failover

It may seem like a daunting task to design a system to run in multiple regions. This is understandable from a traditional, monolithic system point of view. Before the cloud, we did not always expect our systems to run in multiple data centers. We designed them to run in one on-premises data center at a time. The presentation tier assumed that a network connection would always be available. The data tier required strong consistency. Deployments where not automated, so failover was manual and usually involved a time consuming restore of the database from the latest backup. Refitting these brittle systems to run in multiple cloud regions was painful. A primary/cold-secondary topology was usually the best we could achieve.In contract, we have been designing our serverless systems to run in multiple regions all along. In todays highly connect world, the context and expectations for our systems is very different. We have reinvented our system architecture and...