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 ESG services

In Chapter 7, Bridging Intersystem Gaps, we covered the ESG pattern that provides an anti-corruption layer around external systems. The syntactic details of various security technology often differ between system. ESG services encapsulate these details so that they do not pollute the rest of the system. We may even isolate legacy systems and external interfaces in their own cloud accounts to help control the attack surface that exists at the interactions between disparate systems. In this section, we will address shared secrets such as passwords, access keys, and API keys.

Securing shared secrets

The various ESG scenarios require connecting to external resources. We secure these interactions in transit with SSL, but first they must be authenticated. Legacy systems will most likely require a username and password, while modern systems typically require some sort of long-lived token. For example, a SaaS system may use API keys and a cloud provider may require an access...