Menu
REST API design indicates there are four resources archetypes: document, collection, store and controller.
Store do not create new resources; therefore a store never generates new URIs.
An example:
PUT /users/12245/favorites/boston-celtics
A user added Boston Celtics to his favorites list.
But how that isn't creating a new resource ? and how it isnt generating a new URI?
772
The forward slash (/) character is used in the path portion of the URI to indicate a hierarchical relationship between resources.
URL Structure The recommended convention for URLs is to use alternate collection / resource path segments, relative to the API entry point.
Each resource in REST architecture is identified by its URI (Uniform Resource Identifier). A URI is of the following format − <protocol>://<service-name>/<ResourceType>/<ResourceID> Purpose of an URI is to locate a resource(s) on the server hosting the web service.
In this case, we refer to these resources as singleton resources. Collections are themselves resources as well. Collections can exist globally, at the top level of an API, but can also be contained inside a single resource. In the latter case, we refer to these collections as sub-collections.
A store does not create a resource on its own. The user of the store creates endpoints / URIs.
The contrast is between a Collection and a Store
Collection A collection resource is a server-managed directory of resources. Clients may propose new resources to be added to a collection. However, it is up to the collection to choose to create a new resource, or not. A collection resource chooses what it wants to contain and also decides the URIs of each contained resource.
Store A store is a client-managed resource repository. A store resource lets an API client: put resources in, get them back out, and decide when to delete them.
66
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
