Glossary
Every term the courses use, defined in one line and then in a paragraph. Written to be read out of order.
Showing 5 of 5 matching “Client”
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
An API style where the client states what it wants.
One endpoint that accepts a description of the desired data. Fills a rich screen in one round trip with no unused fields, at the cost of much harder caching and rate limiting.
The request-and-response protocol of the web.
The rules by which a client asks and a server answers. A request is a method, a path, headers, and maybe a body; a response swaps the method for a status code. Stateless by default.
See also Status code, Stateless, Endpoint
Any value that grants access.
A database password, an API key, a signing key. Never in code, never in a client bundle. If one leaks, revoke it first. Deleting the line comes second, and git history keeps it regardless.
See also Environment variable, Key rotation
A function you call from the client that runs on the server.
Written like a normal function, but the build replaces the body with a network call in the client bundle and the real implementation only ever exists on the server. You get a typed contract for free and the server code never ships to the browser.
See also RPC, Validation, Secret