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 chapter, you learned why we need observability to fail forward fast and how serverless makes it easier to collect useful metrics. You also learned how to leverage FinOps and cost metrics to help decide when it is worth tuning our services.

We dug into the details, and you learned how to use resources metrics and the USE method, and work metrics and the RED method, to turn observability data into actionable information. You learned how to monitor the frontend with real user monitoring and synthetics. You also learned about continuous performance tuning and reviewed some common tuning tips.

In the next and final chapter, we will round out our discussion on architecting for innovation, with thoughts on getting started, gaining trust, and building momentum. We will address some of the myths and anti-patterns that keep teams from getting off the ground and cover the various hurdles and impediments that teams must confront.

Leave a review!

Enjoying this book...