Glossary
Every term the courses use, defined in one line and then in a paragraph. Written to be read out of order.
Showing 3 of 24 matching “Server”
A kept copy of something expensive to produce.
A stored result reused instead of being recomputed or refetched. The most effective performance tool available and the source of the most confusing bugs, because a copy can be out of date. Copies live in the browser, the CDN, and your server.
See also CDN, Invalidation, TTL
The side making the request, usually a browser.
Whatever asks for something: a browser, a mobile app, another server. Crucially it runs on a machine the user controls, so nothing it claims can be trusted without verification.
See also Server, Validation
The delay when no instance is running yet.
When a serverless function has no live instance, one must be created before your code runs. That startup delay is the price of paying nothing while idle, and it lands on whichever unlucky visitor arrives first.
See also Serverless, Stateless