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

Gaining trust and changing culture

Any new effort that goes against the grain of the current culture will experience a bumpy start. It's normal. But it won't take long for the culture to start changing once the new approach proves its worth. I remember my first lift-and-shift project. It was a long uphill climb, but then things changed, almost overnight.We initially transplanted our manual data center processes into the cloud. But we saw no real benefit from the cloud at that point, because each release of the software was still slow and painful. So, we set out to automate the deployment of the entire platform. We encountered resistance from the start. But we applied our agile, incremental development methodology and started to move forward. First, we did a quick proof of concept and then we addressed incremental pain points as we progressed toward the full solution. Along the way, we picked up support.After a long 6 months, we had all the support we needed, and we were ready...