SVS311: Practical Experience With a Serverless-First Strategy at Capital One

Resources for SVS311: Practical experience with a serverless-first strategy at Capital One

In this session, Capital One shares concrete examples of how they have implemented serverless patterns, challenges they have faced, and the best practices and tips they have learned from operating AWS Lambda at scale in production. Dive deep on scaling Lambda with various event sources, considerations of event source integrations, observability at scale, and failure-handling mechanisms.

SAM Local Invoke

Documentation

This documentation goes through command line parameter options for performing local testing with SAM CLI.

Using Parameter Store parameters in AWS Lambda functions

Documentation

These instructions walk through the setup and configuration process for the Lambda Extension for Parameter Store.

Use AWS Secrets Manager secrets in AWS Lambda functions

Documentation

These instructions walk through the setup and configuration process for the Lambda Extension for Secrets Manager.

Set up API Gateway private integrations

Documentation

Overview of how to implement private backend integrations with API Gateway

Custom domain names for private API Gateway endpoints

GitHub

Sample repository for implementing custom domain names for private endpoints.

Implementing safe AWS Lambda deployments with AWS CodeDeploy

Blog

Overview of using CodeDeploy to perform blue/green or canary deployments of your Lambda functions.

Presented by:

George Mao

George Mao

George leads the Serverless Center of Excellence at Capital One. He is responsible for helping the bank transform into a Serverless-first engineering organization. Before joining Capital One, he spent 7 years at AWS and served as the Head of Solutions Architecture for Serverless computing. George is a VT Hokie and lives in the DC Metro area with his family.

Heeki Park

Heeki Park

Heeki Park is a Principal Solutions Architect at AWS and has been helping customers build serverless and cloud-native applications since joining AWS in 2016.

Follow on LinkedIn