Chaos engineering is a discipline that focuses on improving system resilience through controlled experiments that expose the inherent chaos and failure modes in your system, before these failure modes manifest themselves like a wildfire in production and impact your users. (Netflix is undoubtedly the leader in this field.) However, much of the publicized tools and articles about chaos engineering focus on killing EC2 instances, and efforts to implement chaos engineering in the serverless community have been largely limited to moving those tools into AWS Lambda functions.
But how can we apply the same principles of chaos to a serverless architecture built around AWS Lambda functions?
Serverless architectures have more inherent chaos and complexity than their serverful counterparts, and you have less control over their runtime behavior. In short, there are far more unknown unknowns with these systems. So can we adapt existing practices to expose the inherent chaos in these systems? If so, what are the limitations and new challenges that we need to consider?
Join Yan Cui to learn how to apply the principles of chaos to a serverless architecture.
Yan Cui is a principal engineer at DAZN and an AWS serverless hero. Over his career, he has been an architect and lead developer with a variety of industries ranging from investment banks, ecommerce to mobile gaming. In the last two years, he has worked extensively with AWS Lambda in production, and he has been very active in sharing his experiences and the lessons he has learned.
Yan is polyglot in both spoken and programming languages and counts C#, F#, Scala, Node.js, and Erlang among the programming languages he has worked with professionally. Yan is a regular speaker at user groups and conferences internationally and is the instructor of Production-Ready Serverless and a coauthor of F# Deep Dives. In his spare time, he keeps an active blog at theburningmonk.com.
©2018, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com