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

Securing CI/CD pipelines

Our serverless systems are composed of cloud resources, such as functions, datastores and messaging channels, and we use the cloud provider's deployment service, such as AWS CloudFormation, to automate the creation of these resources. In Chapter 12, Choreographing Deployment and Delivery, we will cover the GitOps flow we follow for deploying these resources via our CI/CD pipelines. But first, we need the permissions to create, update and delete these kinds of resources. Plus, we typically use SaaS CI/CD service, such as GitHub Actions or GitLab-CI, and these services execute outside our cloud accounts.So, we need an approach that limits the permissions that we give to these tools. We accomplish this by creating separate roles for the pipeline service and the deployment service. We will also introduce the concept of permission boundaries.You can find a template for securing your CI/CD pipelines here: