REST
BackendAn API style organised around things.
Endpoints named after resources (/users, /orders) with HTTP verbs saying what to do to them. Highly cacheable and easy to inspect. A rich screen may need several calls.
Glossary
Every term the courses use, defined in one line and then in a paragraph. Written to be read out of order.
Showing 2 of 8 matching “API”
An API style organised around things.
Endpoints named after resources (/users, /orders) with HTTP verbs saying what to do to them. Highly cacheable and easy to inspect. A rich screen may need several calls.
Calling a named function on another machine.
An API style where you invoke an action directly rather than modelling resources. With shared types, a contract break becomes a build error, which is why it suits an app talking to its own backend.
See also Server function, REST, API