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

Securing BFF services

In Chapter 6, A Best Friend for the Frontend, we covered the BFF pattern. These services expose a synchronous interface to the frontend, which means they expose an attack surface at the boundary of the system. Fortunately, securing a serverless BFF service in depth is mostly a declarative exercise. We need to grant access to a service, then grant access to the data, track who did what and ensure a service cannot access resources outside the service. Let's discuss these topics in this order.

JWT authorizer

When we left off in the previous section, Securing the frontend, we passed the user's idToken in a request to a BFF service using the Authorization header. Once a request reaches the BFF service, the first step is to authorize the request. The API gateway performs this step, so that we separate the technical concerns of handling the JWT token from the business logic. This also eliminates unnecessary calls to the query and command functions when the request...