Premium Video

This video is available to premium subscribers only

Unlock Full Access

Running your own services means provisioning servers, planning capacity, patching operating systems, and paying for machines even when they sit idle. For many workloads, that is a lot of work that doesn't directly improve the product.

Serverless architecture hands much of that work to the cloud provider. You write the code, and the platform runs it when needed, scales it, and charges you for what you use. You still own the system design, though: events, retries, limits, cold starts, and cost are all still your problem.

This chapter covers what serverless architecture is, how functions are triggered and scaled, how pricing works, and the trade-offs that come with it.