PM team lead for Ecosystem @ Netlify here. Thanks for the feedback - this is exactly what we're trying to address with Netlify Graph. There is a lot of variability as APIs change, and there's a lot of value in abstracting out that complexity behind a consistent data model.
Comments
From having maintained 60+ API integrations for a B2B business, I can see how Netlify Graph (or previously OneGraph) solves a real problem.
The initial integration is usually straightforward, but the maintanence of these seemingly simple API wrappers is what bites back in the long run.
With having lots of integrations, these are the usual failure points:
1. Teams find it hard to keep track of all the changelogs across APIs.
2. Failing at [1] means that API changes get noticed much later and having to cram the work into product development cycles.
PM team lead for Ecosystem @ Netlify here. Thanks for the feedback - this is exactly what we're trying to address with Netlify Graph. There is a lot of variability as APIs change, and there's a lot of value in abstracting out that complexity behind a consistent data model.