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

Integrating across cloud providers

Polycloud is the notion that we should use the right cloud provider for the job on a service-by-service basis. This is similar to the concepts of polyglot programming and polyglot persistence. We will discuss the business value supporting this approach in Chapter 13, Don't Delay, Start Experimenting. In this section, we will cover the tactical aspect of connecting subsystems that runs across cloud providers.Fundamentally, polycloud is employed at the service level, but from a practical standpoint, it operates at the subsystem level. For example, if you only have a single service that you want to run on a different cloud provider, then we can think of it as a subsystem consisting of a single service. However, there would most likely be several related services that all benefit from running on the alternate cloud provider and others that are just better off running as closely as possible to related services.This subsystem point of view makes integrating...