We use analytics cookies.We use cookies to analyze site traffic and improve your experience.
Loading...
System Design Masterclass · Cloud Infrastructure
Free preview: the first 2 parts of this 8-part lesson.
Already bought the course? Sign in to read the whole lesson.
this lesson is part of
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design courseread the rest of this lesson in
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design coursein Cloud Infrastructure
This lesson is part of the full System Design Masterclass. Unlock it along with 769 other lessons for a one-time payment.
One-time payment by card or PayPal
Get Lifetime AccessOne-time payment: UPI, card or netbanking
Get Lifetime Access18 Foundation lessons are free, no payment needed. Try them now
It is easy and good
“It is really nice and good Please join the course”
In a monolith, your entire application is one deployment. In , each service is a deployment. FaaS takes it further: each function is a deployment.
Why would you want this? Because not every piece of your application has the same scaling needs. Your user signup function might get 100 calls per day. Your image resize function might get 100,000 calls when someone uploads a photo album. Your payment webhook might get 10 calls per hour. With FaaS, each function scales independently. The image resizer gets 100 concurrent instances. The signup function stays at one. You pay proportionally.
FaaS is the compute layer of serverless. Lambda, Cloud Functions, Azure Functions are all FaaS providers. Understanding FaaS means understanding the specific model: how functions are triggered, how they scale, how they connect to other services, and where they break down.
The three major cloud providers each offer FaaS, and they differ in important ways: