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

Providing an Open API and SPI

Non-invasive integration is one of the goals of the ESG pattern. This is important when you do not have control of the other systems. But it means that you are taking on the responsibility of implementing the integrations that adapt the other systems to your system. This is only manageable for a limited number of systems.If you are implementing your own SaaS product, then the number of external systems that want to integrate with your system can be limitless. In this case, the only manageable solution is to provide your own open interface and make the external systems responsible for integrating with your system.Open interfaces expose your external domain model to the outside world. They act as a façade to hide the inner workings and provide strong backward compatibility guarantees. They simplify the process of integrating with your system and enable external systems to take on the responsibility for connecting to your system and transforming between...