Challenge 1: The Lambda-lith

In this post I show how to move from using a single Lambda function as scalable web host with an MVC framework, to a decoupled microservice model.

Challenge 2: The mono-repo

This blog post provides recommendations for designing and managing code repositories in larger serverless projects, and best practices for deploying releases of production systems.

Challenge 3: Enforcing security best practices

Build micro-perimeters to enforce strict verification of every person or service.

As your organization grows, you might want to allow trusted employees to configure and manage IAM permissions to help your organization scale permission management and move workloads to AWS faster.

This post explains how layers work, and how you can build and include layers in your own applications.

Challenge 4: Managing multiple AWS accounts

Use a single pipeline to deploy a microservice into multiple accounts; for example, a microservice must be deployed to environments such as DEV, QA, and PROD, all in separate accounts.

During deployment, a resource deployed into one AWS account may need to refer to a resource deployed in another AWS account.

Microservices executing in one AWS account may need to communicate with microservices executing in another AWS account.

This blog post shows you how to use EventBridge resource policies to publish events and create rules on event buses in another account.

Resources for growing your serverless applications

Use these code examples to help implement some of the best practices described in this session