HATEOAS API: Difference between revisions
Jump to navigation
Jump to search
(Add facebook) |
(Add Shopify) |
||
| Line 31: | Line 31: | ||
| [https://opensource.zalando.com/restful-api-guidelines/#114 Zalando] || style="background:#ffadad"|No || style="background:#caffbf"|Yes || style="background:#caffbf"|Yes || style="background:#ffadad"|No || style="background:#ffadad"|No || style="background:#fdffb6"|? || style="background:#caffbf"|Yes | | [https://opensource.zalando.com/restful-api-guidelines/#114 Zalando] || style="background:#ffadad"|No || style="background:#caffbf"|Yes || style="background:#caffbf"|Yes || style="background:#ffadad"|No || style="background:#ffadad"|No || style="background:#fdffb6"|? || style="background:#caffbf"|Yes | ||
|- | |- | ||
| [https://developers.facebook.com/docs/graph-api/overview Facebook Graph API] || style="background:#ffadad"|No || style="background:#caffbf"|Yes || style="background:#caffbf"|Yes || style="background:#ffadad"|No || style="background:#ffadad"|No || style="background:#ffadad"|No || style="background:# | | [https://developers.facebook.com/docs/graph-api/overview Facebook Graph API] || style="background:#caffbf"|Yes || style="background:#caffbf"|Yes || style="background:#caffbf"|Yes || style="background:#ffadad"|No || style="background:#ffadad"|No || style="background:#ffadad"|No || style="background:#fdffb6"|? | ||
|- | |||
| [https://shopify.dev/docs/admin-api/rest Shopify] (REST) || style="background:#caffbf"|Yes || style="background:#caffbf"|Yes || style="background:#caffbf"|Yes || style="background:#ffadad"|No || style="background:#ffadad"|No || style="background:#ffadad"|No || style="background:#caffbf"|Yes | |||
|} | |} | ||
[[Category: Terminology]] | [[Category: Terminology]] | ||
Revision as of 09:58, 14 January 2021
Originally called REST, HATEOAS is a way of designing HTTP APIs as described in Roy Fieldings thesis. The acronym stands for Hypermedia as the Engine of Application State.
It distinguishes itself from other APIs by having the following properties:
- Heavy use of Media Types to allow Backward Compatibility.
- It does not allow clients to construct URLs (unless instructed by the server to do so) to allow for applications to change their URL structure.
- Other than an entry URL and a set of documents describing the Media Types, no additional knowledge should be necessary to use the API.
HATEOAS APIs usually make heavy use of HTTP features like:
- Caching to enable the application to scale better.
- Content Negotiation to support older clients and give users localized versions of resources.
- Conditional PUTs to add Optimistic Concurrency.
Comparison
| Method | Browser Accessible | Backward Compatible | Backward Compatible (default) | HTTP Cachable | No URL Construction | URL as Identifier | Stable Pagination |
|---|---|---|---|---|---|---|---|
| HATEOAS | ? | Yes | ? | Yes | Yes | Yes | ? |
| media_types-serialization (HATEOAS) | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Github (REST) | Yes | Yes | No | No | Yes | Yes | Yes |
| Zalando | No | Yes | Yes | No | No | ? | Yes |
| Facebook Graph API | Yes | Yes | Yes | No | No | No | ? |
| Shopify (REST) | Yes | Yes | Yes | No | No | No | Yes |