Operations → Cloud Infrastructure
Function as a Service
A serverless compute model where small functions run in response to events or requests.
Motivation
Function as a Service exists because teams need a practical way to solve a recurring problem in real systems. It gives engineers a shared abstraction for discussing trade-offs instead of treating every implementation as unique.
Where it fits
Function as a Service belongs to the operations track in the cloud infrastructure layer. It is useful when reasoning about nearby concepts such as Serverless.
Mental model
Think of Function as a Service as a named design pressure: it usually improves one quality, such as scalability, safety, usability, or operability, while adding constraints that must be understood.
Example in practice
When Function as a Service appears in a system, the important question is not only what it is, but why the system needs it and what failure modes it introduces.
Common mistakes
- Using Function as a Service because it is fashionable rather than because the problem requires it.
- Ignoring the operational cost or learning curve.
- Treating the concept as isolated instead of connecting it to neighboring concepts.