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

Poly everything

We all have our preferences. You prefer a specific programming language, a specific database, and a specific cloud provider. You have lots of experience with them, so you can get the job done fast. Everyone should follow suit. Everyone should just get along and use the same tools and technologies. Or it should be the Wild West, and everyone should be an “outlaw” and do what they want to. Well, of course, neither of these extremes is practical. There are limits. There must be some governance. But as we covered in Chapter 2, Defining Boundaries and Letting Go, governance can impede innovation. So we want a balanced portfolio. We need diversification. We do not want to impede. And we need to be prepared for what might come. Let’s see how we can strike the right balance with a poly-everything approach.

Polyglot programming

Polyglot programming is the idea that we want to use the right programming language for the job at hand. The different...