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

Implementing CEP logic

Up to this point, we have mostly used control services to orchestrate business processes. In the previous examples, an end user initiated a business process via publishing an event from a BFF service. Humans are excellent complex-event processors. We naturally process all kinds of inputs and quickly make decisions, but we aren't always paying attention, or there may be too many inputs to reliably and consistently process them all.This is where we can use control services to perform CEP and emit events to alert downstream services of their findings. The processing logic is considered complex because we are not just reacting to a single event. We collect and correlate multiple events and evaluate conditions across them for actionable insights. For example, we could audit a business process and assert that it is adhering to expectations. We have already seen a basic example of CEP when joining parallel paths in a business process.Let's look at how we can...