I have a question about remote APIs that I’m struggling to find an answer for and I wondered if anyone had any insight or experience. I’ve looked at the relevant sections of various API books and tried various search combinations but I can’t find an answer so I’m wondering if I’m asking the wrong question or if my context is a little niche. Apologies if I’ve missed a vital section in one of the books or blog posts that would give me the relevant “aha!” moment.
1/
Is this because nobody would (should) be mad enough to put such “Application APIs” in a catalogue (possibly because they don’t really understand what “API” means) or am I missing a nuance here?
/end
@Andylongshaw I feel like cataloguing is better than not cataloguing but you’d want to tag them with ‘intended customers’ or else a ‘this is an internal interface’ but …
I suppose a prior question is, who reads the catalogue and why?
@chrisfcarroll it’s a very good question. Currently my take is that the only reason to read the catalogue would be if you are a consumer of one or more of the APIs. That’s the primary purpose, hence only wanting to catalogue those APIs / interfaces that are open to reuse. There could be some secondary justification around security checking etc but that’s yet to emerge and I want to avoid blue-sky thinking that creates extra work.
@Andylongshaw Yes, “avoid blue-sky thinking that creates extra work” seems like a great rule of thumb , I shall steal it and use it often!👍
