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

Zigzagging through time

The presentation tier is a battleground. It always has been. It always will be. It is the most visible part of a system, so it elicits the most feedback and experiences the most churn. From a functional perspective, this is good, because it leads to innovations that help us zero in on the right solutions for users. From a technical perspective, this volatility is more of a mixed bag.Today, a technical war rages over the use of the React framework versus the Angular framework. It is good to have choices and the competition drives technical innovation that benefits everyone. But it can also create a skills gap that impedes progress when team members move between projects that use different frameworks. We will provide some relief for this problem in the Dissecting micro frontends section, but I suspect we will never end the framework wars. However, debates over things such as client-side versus server-side rendering are more clean-cut. Let's see how.