Differences

This shows you the differences between two versions of the page.

--- api [2019/03/21 10:57] – skipidar
+++ api [2023/12/01 21:27] (current) – skipidar
@@ Line 7: / Line 7: @@
+==== Communication options =====
+{{https://s3.eu-central-1.amazonaws.com/alf-digital-wiki-pics/sharex/rNvZHNhbje.png}}
 ==== 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:API  ===
+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 ====
 === Spring HATEOAS ===
@@ Line 69: / Line 87: @@
   * https://dzone.com/articles/json-api-using-katharsis-amp-spring-boot
-  * There are also libs, which generate a JSON:API conform API from Resources and Data Access Objects
+  * There are also libs, which generate a JSON:API conform API from Resources and Data Access Objects. E.g. https://dzone.com/articles/json-api-using-katharsis-amp-spring-boot
-E.g. https://dzone.com/articles/json-api-using-katharsis-amp-spring-boot
+  * There is a detailed description of the API structure, separated from the implementation: https://jsonapi.org/ 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 detailed description of the API structure, separated from the implementation: https://jsonapi.org/
+  * There is a JSON Schema, helping to validate our APIs automagically E.g. https://jsonapi-validator.herokuapp.com/
-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://jsonapi-validator.herokuapp.com/