3 ms·
The other mistake that I've seen people make is to try to build their application completely on top of a public API. Sometimes you want to do things in your ap
by mason55 13y ago
The other mistake that I've seen people make is to try to build their application completely on top of a public API. Sometimes you want to do things in your application that, either for security or scaling reasons, you don't want someone consuming the public API to be able to do (bulk operations, administrative functions, cross-account updates, etc).
You either need private API functions or you need to allow actions that aren't triggered by an API call.
- jqueryin 13y agoI didn't discuss this in the article, but I should note we do indeed have a fully private API that functions independent of the other and is utilized by our administrative management tools.
- johns 13y agoOur public API is a front end for our other services with auth added on and better guarantees against breaking. We don't depend on it directly for anything public facing and I wouldn't suggest anyone completely rely the same API they offer partners/openly to avoid getting into a tough spot with managing changes.