AWS Lambda and #serverless. What’s all the fuzz about?

A talk about serverless and Function-as-a-Service I gave at the European Chaos Engineering Days at KTH, December 2018.

Transcript

1. Joint work with Erik Wittern and Waldemar Hummer Josef Spillner AWS Lambda and #serverless. What’s all the fuzz about? Philipp Leitner philipp.leitner@chalmers.se @xLeitix
2. Chalmers !2 https://icet-lab.eu @IcetLab We are hiring a postdoc!!
3. Chalmers !3 Function-as-a-Service?
4. Chalmers !4 Function-as-a-Service? Serverless?
5. Chalmers !5 Source: https://aws.amazon.com/lambda/
6. Chalmers !6 Source: https://aws.amazon.com/lambda/
7. Chalmers !7 Source: https://aws.amazon.com/lambda/
8. Chalmers !8 Source: https://aws.amazon.com/lambda/
9. Chalmers !9 Source: https://github.com/aws-samples/lambda-refarch-streamprocessing An Example: Real-Time Tweet Processing
10. Chalmers !10 Internally Container Runtime Events (e.g., client requests, system events, triggers…) User/tenant datastore Execution datastore e e e … Execution Queue Result data Function Controller Function datastore Function source code Function container <fn> Event Controller … Load balancer Authentication Rule engine Authorization Function container <fn> Function container <fn> Source: loosely based on IBM’s OpenWhisk architecture
11. Chalmers !11 No state
12. Chalmers !12 No state Hard cap on max. execution time
13. Chalmers !13 No state Hard cap on max. execution time Extreme tail latency
14. Chalmers !14
15. Chalmers !15 Methodology Interviews (n = 12) Analysis of Grey Literature (n = 50) Web Survey (n = 182)
16. Chalmers !16 Main Findings Compositional Application Model “Microservices on steroids”
17. Chalmers !17 Source: https://github.com/aws-samples/lambda-refarch-streamprocessing Recall: Real-Time Tweet Processing
18. Chalmers !18 Compositional Application Model
19. Chalmers !19 Main Findings Compositional Application Model Use Cases
20. Chalmers !20 Main Findings User-Facing 27 (29%) Backend 29 (31%) Both 38 (40%) But: many challenges in user-facing apps
21. Chalmers !21 Use Cases - Backend
22. Chalmers !22 Main Findings Compositional Application Model Use Cases Challenges
23. Chalmers !23 Challenges
24. Chalmers !24 The Future (as we see it) “Faster horses” Different Services vs (end user view) (provider view)
25. Chalmers !25 The Future (as we see it) Different Services “Function-as-a-Service as the assembly language of the cloud”
26. Chalmers !26 The Future (as we see it) Different Services “Function-as-a-Service as the assembly language of the cloud”
27. Chalmers !27 Learn More https://peerj.com/preprints/27005/