Building resilient serverless workloads: Navigating through failures

My talk "Building resilient serverless workloads:
Navigating through failures"
from AWS Community Day DACH

1. Building resilient serverless workloads: Navigating through failures JIMMY DAHLQVIST | 2024-09-17

2. Building resilient serverless workloads: Navigating through failures JIMMY DAHLQVIST | 2024-09-17

3. Thank You!

4. JIMMY DAHLQVIST Head of AWS @ Sigma Technology Cloud Founder of serverless- handbook.com AWS Serverless Hero ☁️ User Group Leader ☁️ AWS Ambassador   § Hello, I'm

5. Resources https://serverless-handbook.com Architecture patterns Solutions Workshops

6. Agenda What is serverless and resiliency Architecting resilient system – Good practices Summary What did you learn?

7. What is serverless? Automatic and flexible scaling No capacity planning High Availability Pay-for-use billing

8. What is resiliency? The ability for a software solution to handle the impact of problems, and recover from turbulent conditions, when other parts in the system fails.

9. “Everything fails all the time Dr. Werner Vogels , CTO, Amazon.com

10. Understand AWS Services Everything has a limit Understand how services work under the hood

11. Resiliency testing (in prod- ish ) Chaos Engineering Amazon Fault Injector Service Start in QA Don’t forget about data

12. Web application

13. Do we need an immediate response?

14. Storage-First

15. Storage-First Data-centric design Durability and availability Scalable System Design Asynchronous processing

16. Storage-First Things to consider Architectural complexity Eventual consistency Design for idempotency Risk of over-optimization

17. Queue Load Leveling

18. Queue load leveling System stability Handle unexpected spikes Protect downstream resources

19. Decoupling

20. Decoupling

21. Retries Selfish Exponential backoff Users can make it worse

22. Retries with backoff and jitter No Jitter With Jitter Image: Amazon Architecture blog (https:// tinyurl.com /y48t2v4h)

23. DLQ

24. DLQ

25. Circuit breaker

26. Circuit breaker Half Open

27. Circuit breaker Avoid cascading failures Protect system resources Risk of early circuit break Good observability required

28. Put it all together

29. Notification Service Payment Service

30. What we talked about Design for failure Buffer and store messages first Process asynchronously Level the load Retry on failures Break if integrations are not healthy

31. Quiz with me!

32. @jimmydahlqvist dahlqvistjimmy https://serverless- handbook.com https:// jimmydqv.com THANK YOU

33. @jimmydahlqvist dahlqvistjimmy https://serverless- handbook.com https:// jimmydqv.com PLEASE FILL IN THE SESSION SURVEY

34. PLEASE FILL IN THE SESSION SURVEY