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, we learned that modern systems need to work in an eventually consistent world and that eventual consistency is based on transparency, facts, and a well-crafted chain reaction of atomic actions. You learned how to increase team confidence by using an event hub to create an outbound bulkhead between upstream and downstream services, and how the event sourcing pattern turns events into facts by saving them in perpetuity in an event lake.

We dug into the details, and you learned how to implement fault-tolerant stream processors and optimize a subsystem’s messaging channel topology. Also, you learned how to optimize throughput with techniques such as multiplexing, pipelining, asynchronous non-blocking I/O, and sharding.

In the next chapter, we will cover the Command Query Responsibility Segregation (CQRS) pattern and see how it helps us fight data gravity, by implementing a data life cycle architecture that turns the database inside out and creates...