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

Leveraging FinOps

Cost is always a primary concern, particularly when teams are first venturing into the serverless arena. But serverless, not only turns observability inside out, it turns the concern for cost on its head. Instead of worrying about cost, we will leverage it as a powerful tool for self-governance, that enables autonomous teams to continuously tune and optimize their subsystems.Let's see how we can use cost as a metric, dissect the typical monthly serverless cloud invoice, and explore worth-based development and tuning.

Cost is a metric

Cost was not a very useful metric back when I first started building and running systems in the cloud, well before serverless came around. In those days my monthly cloud bill just told me how many hours of AWS EC2 instances and AWS RDS databases I had used. Those values were very monolithic. They did not tell me how I was using those instances and databases. They did not tell me how well I was utilizing those resources. And they certainly...