Money-saving tips for the frugal serverless developer

Join us in this insightful session as we dive into the world of serverless architectures and explore common cost mistakes and learn actionable tips for cutting down wastes and reducing your AWS bill.

Whether you're looking to cut down on CloudWatch costs or improve cost-efficiency for your serverless application, we've got some helpful tips, just for you.

Transcript

1. Money saving tips for the frugal serverless developer Yan Cui @theburningmonk
2. “serverless”
3. “serverless”
4. www.cloudzero.com/blog/our-take-on-the-new-stack-survey
5. serverless is
6. serverless is SCALABLE
7. serverless is RESILIENT
8. serverless is SECURE
9. COST-EFFICIENT serverless is
10. AWS is hard.
11. Mistakes can be expensive.
12. Yan Cui http://theburningmonk.com @theburningmonk AWS user since 2010
13. Developer Advocate @ Yan Cui http://theburningmonk.com @theburningmonk
14. Independent Consultant advise training delivery Yan Cui http://theburningmonk.com @theburningmonk
15. Billing alarms
16. Everyone should use billing alarms.
17. They are not perfect. But they can still save your a$$.
21. Keeping monitoring cost under control
22. CloudWatch often cost much more than your core application.
23. As cost goes up, value goes down.
24. How to keep CloudWatch Logs cost under control 1. Do structured logging.
25. How to keep CloudWatch Logs cost under control 1. Do structured logging. DEBUG INFO WARN ERROR Detailed events for debugging application. General information that highlights progress of application. Potential problems, but doesn’t stop application from working. Issues that require immediate attention.
26. How to keep CloudWatch Logs cost under control 1. Do structured logging. Log at INFO or above in production. DEBUG INFO WARN ERROR Detailed events for debugging application. General information that highlights progress of application. Potential problems, but doesn’t stop application from working. Issues that require immediate attention.
27. How to keep CloudWatch Logs cost under control 1. Do structured logging. Log at INFO or above in production. 2. Sample DEBUG logs in production. e.g. 5% of invocations.
28. How to keep CloudWatch Logs cost under control 1. Do structured logging. Log at INFO or above in production. 2. Sample DEBUG logs in production. e.g. 5% of invocations. 3. Set log retention to 30 days.
30. CloudWatch Logs AWS Lambda AWS Lambda stdout asynchronously invokes any log aggregation service
32. CloudWatch Logs AWS Lambda AWS Lambda stdout asynchronously invokes any log aggregation service double paying for logs
33. Lambda Extensions + Telemetry API
34. https://docs.aws.amazon.com/lambda/latest/dg/telemetry-api.html
36. CloudWatch Logs AWS Lambda
37. https://lumigo.io/blog/lumigo-launches-log-management
43. DEBUG INFO WARN platform.initStart platform.start platform.initRuntimeDone platform.initReport platform.runtimeDone platform.report unhandled exception
44. DEBUG INFO WARN platform.initStart platform.start platform.initRuntimeDone platform.initReport platform.runtimeDone platform.report unhandled exception
45. Right-sizing Lambda memory
46. More memory = more CPU = more network bandwidth
48. Easy to be wrong by an order of magnitude.
49. STORY TIME
52. Right-sizing Lambda functions
53. https://github.com/alexcasalboni/aws-lambda-power-tuning
54. Use ARM architecture
55. Use ARM architecture (after testing…)
56. 25% cheaper
57. Best for functions with a lot IO wait time.
58. No lambda-to- lambda invocations
63. SYNCHRONOUS Lambda-to-Lambda are almost always a sign of bad design.
65. Service Boundary
66. Service Boundary
67. Service Boundary
68. AWS Lambda function !== lambda function in programming
70. ?
71. ? ?
73. Caching
74. Caching is a cheat code for building performant & scalable applications.
75. bit.ly/sls-caching
76. aaronstuyvenberg.com/posts/containers-on-lambda
77. www.usenix.org/system/ fi les/atc23-brooker.pdf
78. bit.ly/social-network-in-4-weeks
79. average 99% cache hit rate
81. Route53 TTL
83. Use longer TTL for stable domains
84. Avoid CORS
85. Enabled CORS for API Gateway is easy
86. Enabled CORS for API Gateway is easy But you still pay for those CORS requests!
88. You might be double paying for every user request to your API…
90. Choose the right service
91. Every architectural decision is a buying decision.
92. Using the wrong service can be very costly.
95. www.thefrugalarchitect.com
96. Law I. Make Cost a Non-functional Requirement. Law II. Systems that Last Align Cost to Business. Law III. Architecting is a Series of Trade-offs. Law IV. Unobserved Systems Lead to Unknown Costs. Law V. Cost Aware Architectures Implement Cost Controls. Law VI. Cost Optimization is Incremental. Law VII. Unchallenged Success Leads to Assumptions.
97. Law I. Make Cost a Non-functional Requirement. Law II. Systems that Last Align Cost to Business. Law III. Architecting is a Series of Trade-offs. Law IV. Unobserved Systems Lead to Unknown Costs. Law V. Cost Aware Architectures Implement Cost Controls. Law VI. Cost Optimization is Incremental. Law VII. Unchallenged Success Leads to Assumptions.
98. IOT core AppSync API Gateway Messages Connection Time $2 per million $0.08 per million mins $0.25 per million mins $1 per million $0.08 per million mins $1 per million
99. Users Connection Time
100. Users Connection Time Revenue
101. Users Connection Time Revenue Engagement
102. Users Connection Time Revenue Engagement
103. www.gomomento.com/services/topics
105. IOT core AppSync API Gateway Messages Connection Time $2 per million $0.08 per million mins $0.25 per million mins $1 per million $0.08 per million mins $1 per million Momento - - Data Transfer $0.5 / GB EC2 rates EC2 rates EC2 rates
106. Simplify your architecture
107. Avoid unnecessary moving parts to your architecture.
108. ? ?
109. ? ?
110. The most dangerous phrase in the language is "we've always done it this way". - Grace Hopper
111. Function URLs
113. If you’re not using API Gateway features (e.g. Cognito authoriser, request models, direct integration)
114. Or, if you’re facing API Gateway limits (e.g. 29s timeout, no response streaming)
115. Have to write Lambdaliths
116. Have to write Lambdaliths (No per-endpoint metrics & alerts, no fi ne-grained access control, no per-endpoint auth)
117. Have to write Lambdaliths (No per-endpoint metrics & alerts, no fi ne-grained access control, no per-endpoint auth) (Large frameworks a ff ect cold start performance)
118. Best for public or internal APIs
120. Functionless
122. No Lambda = no cold starts
123. bit.ly/social-network-in-4-weeks
124. No API
126. https://theburningmonk.com/2023/12/direct-access-for-frontend-apps-to-aws-services
129. Only allow access if hash key matches cognito sub
130. Not for the feint hearted…
131. When not to use this:
132. 1. Billing alarms 2. Keeping monitoring cost under control 3. No Lambda-to-Lambda calls 4. Caching 5. Route53 TTL 6. Choosing the right service 7. Simplify your architecture 8. Function URLs 9. Functionless 10.No API
133. productionreadyserverless.com Join 20+ AWS Heroes & Community Builders and 1000+ happy students in levelling up your serverless game.
134. “You could spend tens of thousands on costly mistakes, and years of dev time to learn these lessons, or you could spend a few days downloading Yan's extensive experience. The choice is clear!”
135. Questions?