Re:How to Design Better APIs
by cies on Saturday March 12, 2022 @04:38AM
(#30650242)
While I totally agree with the overkill that REST can be, I really do NOT agree with your statement:
> but it requires another API specification
This implies API-specs are part of the problem; and I think they are not.
Specs that have generators for client-libs (and sometimes even sever-stubs) are verrrrry important. They allow us to get some form of type-safety over the API barrier which greatly reduces bugs.
One big reason for me to go with REST is OpenAPIv3: it allows me to completely spec my API and generate clients-libs for sooo many languages, and server-stub for sooo many BE frameworks. This, to me, may weight up to the downsides of REST.
GraphQL is also picking up steam and has these generators.
JSON-RPC (while great in terms of less-overkill-than-REST) does not have so much of this.
> but it requires another API specification
This implies API-specs are part of the problem; and I think they are not.
Specs that have generators for client-libs (and sometimes even sever-stubs) are verrrrry important. They allow us to get some form of type-safety over the API barrier which greatly reduces bugs.
One big reason for me to go with REST is OpenAPIv3: it allows me to completely spec my API and generate clients-libs for sooo many languages, and server-stub for sooo many BE frameworks. This, to me, may weight up to the downsides of REST.
GraphQL is also picking up steam and has these generators.
JSON-RPC (while great in terms of less-overkill-than-REST) does not have so much of this.