Resources
Since our frontend and backend are separate, we need to communicate the state and data between the two. In the frontend, we will need to show all available entities for the service we are providing. These entities are called resources.
Consider a server that provides us with a REST interface (REST API) that has a list of books in our personal library. In this case, list of books are resources and we can request information about each of them from the backend at particular endpoints. For our example, the endpoint can be <URL>/api/books. /api prefix is a convention generally used in REST applications to express that we are interacting with the backend URLs. The resources can generally be thought of as a collection of data, like rows ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access