4 ms·
Well, its a fancier API tool, which smooths out the flow between Backend and API consumers better (at a cost). At its core, it is a project based around a _con
by KuhlMensch 8y ago
Well, its a fancier API tool, which smooths out the flow between Backend and API consumers better (at a cost).
At its core, it is a project based around a _consumer facing schema_, that can be queried. You put in upfront and ongoing be work to give product/frontend/clients the ability to discuss data requirements around a first-class schema, and then once the resolvers are written, allow them to explore/experiment with the data, in queries that can be used directly in production.
From what I have seen, the first (only?) ones to feel the pain it solves for are Product/Frontend/Clients.
Hopefully that ^ waves away some of the haze
- jcroll 8y agoI believe it makes life easier for consumers. What about if you have to maintain the api? And if it is that much harder to maintain is it really a smart choice unless the surface area of your api is the size of say Facebook's?