The motivation of this talk is to provoke the audience to think about the failure modes that exists in their serverless architecture and how they can discover them early by applying the principles of chaos engineering. Serverless architectures have more inherent chaos and complexity than their serverful counterparts, and, we have less control over their runtime behaviour!
Smaller unit of deployment, means there are more of them, and each of these “units” is a boundary that needs to be hardened (for security and failure resilience)
It’s more difficult to harden around the boundaries simply because there are so many more of them
More intermediate services (dynamodb, kinesis, SNS, S3, API Gateway to name a few), each with their own failure modes
There are more configurations overall (timeout, IAM permissions, application config, etc.) therefore more opportunities for misconfiguration
Yan is an experienced engineer who has run production workload at scale in AWS for nearly 10 years. He has been an architect and principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. He has worked extensively with AWS Lambda in production, and has been helping various UK clients adopt AWS and serverless as an independent consultant.