Managing APIs like dependencies, with a package manager-like developer experience. (npm for APIs). The number of APIs is continuously growing. It's going to be impossible to manually manage API dependencies in the future. I wrote about our approach to solve the problem here: https://docs.wundergraph.com/docs/architecture/manage-api-de... I'm curious what others think of this problem space.
This is a small thing, but one of the first sentences in the documentation you linked is "At least I have never thought about API dependencies before building WunderGraph." It makes the problem seem small, as if you can get away with not thinking about it.
Creating an API documentation and (decentralized micro)payment standard might be worthwhile. The hug library made a great impression on me: https://www.hug.rest/
>It's going to be impossible to manually manage API dependencies in the future.
This feels like a significantly important assumption to truly prove out with target customers before relying on this assumption to build a product or business.
I'd love to hear more on what's changing in the future that may make this statement partially or fully true.
I've been thinking about this from a slightly different angle (https://github.com/hofstadter-io/hof), but I think we are both getting at a higher level of reuse and dependency management. I just don't think we need to limit the idea to APIs, there are different granularities, both bigger and smaller, where the ideas are useful.
