A static archive of Markus Tacker's tweets. Follow me on Mastodon: @[email protected].
Looking at
https://blog.falcross.com/introducing-restyped-end-to-end-typing-for-rest-apis-with-typescript/
I wonder if this is a (absolutely well done) solution to the wrong problem.
Do I really want to interact with plain REST APIs these days? As a developer,
usually not and as an API provider I have even more hesitations to advocate
this.
These days REST is but a subset of API technologies and handing a REST API out
as a contract to your service will limit your ability to evolve it in the
future.
I would rather provide high-level SDKs for language that encapsulates your
underlying communication mechanism.
Let this SDK focus on immutable domain entities and operations (not on resources
and whether to POST or to PUT).
An SDK is so much more powerfull in providing an expressive and meaningfull API,
including the communication of deprecated methods, typings, because it can be
written to suit your domain, and does not neet to fit in the REST vocabulary.