GraphQL has become a valuable tool for working with the rather complex APIs that modern microservice applications often have.
It has been increasingly adopted as a preferred query language for working with APIs. Thousands of companies like Audi, Airbnb, Coursera, Expedia, DailyMotion, GitHub, Facebook, Twitter, The New York Times all use GraphQL
GraphQL returns data from a single endpoint in a way that is a better fit for the way that IDM drivers process data, rather than forcing IDM to query collate and deduplicate data from many REST endpoints.
There are specific deficiencies in the REST driver as it ships today that mean that it cannot be 100% used as a basis for a GraphQL integration. (I have tried, mostly succeeded, but it is not perfect!)
In particular, GraphQL rolls it's own error reporting and does not always follow the RESTful logic of reporting errors via HTTP Status Codes.
It should not be particularly difficult to implement a GraphQL Client - driver that builds upon the REST driver shim.
This could be a great addition to the REST/SCIM/SOAP family of "tools" drivers.
Top Comments