3 ms·
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
by dmitriid 6y ago
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.
- rrook 6y agoSounds 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.
- dmitriid 6y agoIndeed, 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.