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

Failing forward fast

Observability is a multi-faceted topic. It can mean different things to different teams. Traditionally, observability has focused on monitoring infrastructure. However, with our serverless systems, we are delegating that responsibility to the cloud provider. This means that we can use observability at a higher order and apply it to help us drive innovation and deliver business value. In other words, observability can help us drive down lead time and move faster.

In Chapter 1, Architecting for Innovation, we dissected lead time so that we can understand what causes it to increase. For example, teams will naturally put on the breaks and slow down when they fear that a change could inadvertently break another part of the system. This is why we build bulkheads throughout our systems.

Teams will also slow down when they do not have enough information about the health and performance of the system. No process is perfect. We cannot eliminate honest human error...