4 ms·
In my experience, most APIs my teamed designed/built were not meant to ever be publicly available. That is, we never considered public availability as a design
by mxz3000 5y ago
In my experience, most APIs my teamed designed/built were not meant to ever be publicly available. That is, we never considered public availability as a design factor. So I think this rule doesn't actually apply anymore.
Then again, I don't know how public availability would change the API design really...
- nivertech 5y agoAPI design concerns for public availability (just to name a few): - security - preventing abuse - API Anti-Corruption Layer - sanitizing inputs and outputs - i.e. not exposing DB IDs/PKs, or pagination cursors directly - versioning, backward- and forward- compatibility, deprecation strategy - usability, DX, Documentation - reducing bandwidth use: - caching - eliminate over-fetching - efficient wire format