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


In this final chapter, we covered some final thoughts on making progress on the path of architecting for innovation. We covered the importance of gaining trust and building momentum, as well as constructing an architectural runway. We also learned how to mold our funding model into our process of continuous experimentation and discovery. We dug into the Strangler pattern and how it reduces migration risk, and we addressed common misconceptions about the event-first approach. We also learned how polyglot programming, polyglot persistence, and polycloud help us optimize a system as a whole and prepare for the future.

As a next step, give the various templates a try. Create an event hub and stand up a micro frontend. Then, create a micro-app and a BFF service. Wrap an external system with an ESG service, and have it react to the events from the BFF service, and vice versa. Along the way, start thinking about your system and how you would divide it into autonomous subsystems...