api
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| api [2019/03/21 10:58] – [Implementation] skipidar | api [2023/12/01 21:27] (current) – skipidar | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| + | ==== Communication options ===== | ||
| + | |||
| + | {{https:// | ||
| ==== IDEA ==== | ==== IDEA ==== | ||
| Line 18: | Line 21: | ||
| + | |||
| + | |||
| + | ==== Standard ==== | ||
| + | |||
| + | === HAL - Hypermedia api langauge === | ||
| + | |||
| + | HAL really is just a document format for a hypermedia API, like HTML is for hypertext. It doesn’t tell you how to express your domain model, and doesn’t really tell you how to use HAL to submit changes. | ||
| + | |||
| + | |||
| + | === JSON: | ||
| + | Whereas JSON API is almost like an “ORM over HTTP”, HAL does a lot less for you though, so it’s not really an apples-to-apples type of comparison. | ||
| + | |||
| + | HAL really is just a document format for a hypermedia API, like HTML is for hypertext. It doesn’t tell you how to express your domain model, and doesn’t really tell you how to use HAL to submit changes. | ||
| Line 42: | Line 58: | ||
| ==== Implementation ==== | ==== Implementation ==== | ||
| + | |||
| + | |||
| === Spring HATEOAS === | === Spring HATEOAS === | ||
| Line 70: | Line 88: | ||
| * There are also libs, which generate a JSON:API conform API from Resources and Data Access Objects. E.g. https:// | * There are also libs, which generate a JSON:API conform API from Resources and Data Access Objects. E.g. https:// | ||
| - | * There is a detailed description of the API structure, separated from the implementation: | + | * There is a detailed description of the API structure, separated from the implementation: |
| - | It gives me the possibility to design equally structured APIs, even when using different technologies. (Can mix up e.g. serverless implementations with e.g. Spring) | + | * There is a JSON Schema, helping to validate our APIs automagically E.g. https:// |
| - | * There is a JSON Schema, helping to validate our APIs automagically | + | |
| - | E.g. https:// | + | |
api.1553165891.txt.gz · Last modified: (external edit)
