1. 7 Things
you need to know
before going serverless
Efi Merdler-Kravitz, Director of Engineering
@TServerless

2. Who am I
2
Part of my expertise is building the dev pipeline in Lumigo.
Working a lot with companies on the subject.
Don’t hesitate to ask me questions

3. Lumigo.io
3
A monitoring and
troubleshooting
platform for
serverless
applications

4. 4
Design Dev Test Deploy Monitor Trace Learn

5. 5
1. DESIGN

6. COLD
STARTS
DESIGN
6

7. COLD STARTS
Taken from: AWS re:Invent 2017: Become a Serverless Black Belt: Optimizing
Your Serverless Appli (SRV401)
https://www.youtube.com/watch?v=oQFORsso2go&feature=youtu.be&t=8m5
s
DESIGN
a. Occurrence Depends
b. Impact up to 15 sec (!)
7

8. COLD STARTS RECOMMENDATIONS
DESIGN
Is it relevant to you?
8

9. DESIGN
Keep Lambdas warm
https://www.npmjs.com/package/lambda-warmer by @jeremyDaly or https://github.com/FidelLimited/serverless-plugin-warmup
9
COLD STARTS RECOMMENDATIONS

10. DESIGN
Reduce package size
10
COLD STARTS RECOMMENDATIONS
http://bit.ly/ColdStartResearch
Reduce initialization time

11. DESIGN
Prefer Python / Node / Go over Java / .NET
11
COLD STARTS RECOMMENDATIONS

12. DESIGN
LAMBDA
CONCURRENCY
12

13. DESIGN
LAMBDA CONCURRENCY
Overview
https://docs.aws.amazon.com/lambda/latest/dg/limits.html
13

14. DESIGN
LAMBDA CONCURRENCY
How to estimate?
Concurrency = average execution
duration in seconds * invocations per
second
14

15. 13-Feb-19
CONCURRENCY
RECOMMENDATIONS
DESIGN
LOAD TEST !
15
https://github.com/Nordstrom/serverless-artillery serverless artillery

16. 13-Feb-19
DESIGN
LOAD TEST !
DON’T
(In production)
16
CONCURRENCY
RECOMMENDATIONS

17. 13-Feb-19
DESIGN
https://docs.aws.amazon.com/lambda/latest/dg/scaling.html
17
MONITOR
“ConcurrentExecutions”
“Throttles”

18. DESIGN
18
CONCURRENCY RECOMMENDATIONS
Need more Lambda concurrency?
Ask AWS to increase limits

19. DESIGN
19
CONCURRENCY RECOMMENDATIONS
Need more Lambda concurrency?
Reduce duration

20. DESIGN
20
CONCURRENCY RECOMMENDATIONS
Need more Lambda concurrency?
Set limits

21. 13-Feb-19
2. DEV ENVIRONMENT
21
1. DESIGN

22. DEV
22
Single Vs Multiple
Shared environment
• Cost effective
• But hard to manage
Environment per developer
• Harder to control cost
• But you don’t step on each other toes

23. Maintain visual
Map of the
architecture
https://cloudcraft.co/
DEV
23

24. 13-Feb-1924
2. DEV
1. DESIGN
3. TEST

25. TEST
25
Test in the cloud (not locally)

26. 13-Feb-1926
2. DEV
1. DESIGN
3. TEST
4. DEPLOY

27. DEPLOYMENT RECOMMENDATIONS
Use gradual deployments
27

28. DEPLOYMENT RECOMMENDATIONS
28
Infrastructure as code

29. DEPLOYMENT RECOMMENDATIONS
29
Allow each developer to easily provision their environment

30. 13-Feb-1930
2. DEV
1. DESIGN
3. TEST
4. DEPLOY
5. MONITOR

31. Consider ELK or other logs
aggregator
MONITOR
31

32. Define CW alerts:
• Errors above threshold
• Concurrency
• Timeouts
• Memory
• Iterator age (if applicable)
MONITOR
32

33. 13-Feb-19
MONITOR
Monitor costs
33

34. 13-Feb-1934
2. DEV
1. DESIGN
3. TEST
4. DEPLOY
5. MONITOR
6. TRACE

35. TRACE
35
Understand your story

36. 36
2. DEV
1. DESIGN
3. TEST
4. DEPLOY
5. MONITOR
6. TRACE
7. LEARN

37. LEARN
LEARN
37
Yan Cui
@theburningmonk
Developer Advocate @Lumigo
James Beswick
@jbesw
Developer
Advocate @AWScloud Serverless
Jeremy Daly
@jeremy_daly
AWS Serverless Hero/ & host
of @ServerlessChats.

38. THANK YOU
efi@lumigo.io | @TServerless