Re:Why not use GraphQL?
by dmitriid on Saturday November 07, 2020 @09:32AM
(#25015254)
One good fit we may have found is for back office/admin.
In a company you often have APIs geared for client apps, and then internal APIs between services. But rarely anyone develops good APIs for backoffice. And then you have an admin interface struggling to retrieve the data it needs from a dozen different API calls.
Slap a simple GraphQL server in front of these dozen calls, and you have a more streamlined development for internal tools.
Re:Why not use GraphQL?
by rrook on Saturday November 07, 2020 @12:31PM
(#25016587)
Sounds like you agree with the OP; " But rarely anyone develops good APIs for backoffice" describes an organizational problem, and the way you've described using GQL does indeed sound like it's bandaiding that problem.
Re:Why not use GraphQL?
by dmitriid on Saturday November 07, 2020 @01:34PM
(#25017227)
Indeed, this is more of an organisational problem and the question of what to prioritise next. Backoffice is usually de-prioritised in favor of customer-facing features.
In a company you often have APIs geared for client apps, and then internal APIs between services. But rarely anyone develops good APIs for backoffice. And then you have an admin interface struggling to retrieve the data it needs from a dozen different API calls.
Slap a simple GraphQL server in front of these dozen calls, and you have a more streamlined development for internal tools.