communication in the service and api supply chain
Another thought about “the service and api supply chain” —how do we know what an API provider or servicer can do? It’s unlikely that any given servicer of an API will service the same subset of that API as any other servicer or be able to keep up with all the changes that are introduced by the API originator.
Can you ask an API endpoint:
- Hey, what can you do?
- What APIs do you originate and provide?
- What 3rd party APIs do you service?
- What subset of those APIs?
- What are your SLAs?
Can the API endpoint tell you:
- I’m running out of capacity to service X?
- There’s a degradation of service Y?
- You can send these calls to these other endpoints I own?
- This is how much I charge per call for Z?
We could use a (roughly) global language with some basic terms for services that describe what they do, what they service, how they do it, with what kinds of commitments. An analog to Wolfram Language for distributed services.
We could use a (roughly) global protocol for handshakes and mutual understanding so services can talk to each other, advertise and discover what they can do, what they can service, how they do it, with what kinds of commitments and interrogation mechanisms. An analog to ethernet autonegotiation for distributed services.
Plenty of API providers don't want this to exist. But the competitive advantage that could be generated by programatically dealing with an API should draw a significant ecosystem. So I wonder why this hasn't been done, especially be near-first tier providers like GCE and Azure. I can only guess it's because they haven't figured out how to do ecosystem-based strategic gameplay for cloud services yet. And of course, AWS has no need to do such a thing (yet).