Serverless functions
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
use functions where they fit and avoid them where they do not.
Planned topics
- Fit: event-driven work, spiky or rare traffic, glue code, scheduled tasks.
- Strengths: no servers to manage, scale to zero, pay per use.
- Limits: execution time, cold starts, concurrency limits, harder local testing, vendor-specific triggers.
- Poor fit: long-running steady load, where per-run pricing exceeds a continuous instance, and latency-sensitive paths affected by cold starts.
- Watch downstream limits: functions can scale faster than your database.
Draft outline details
Demonstration
a cost sketch: break-even between function pricing and a small container as requests per second rise (illustrative; verify prices before recording).
Check your understanding
Which workload suits functions poorly?
Show answer
Long-running steady load.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.