Support GraphQL as an alternative to Kusto
Lots of work being done in GraphQL that are well aligned w what is done via Kusto and gets to a more common language and structure. Agreed gql is more complex than Kusto, but be helpful.
The Azure Resource Graph (ARG) team is actively investigating the scenarios around supporting GraphQL for querying ARG. To help us better understand the use-cases and to determine which implementations may be viable to address the scenarios, we would appreciate if you could fill out this 5-minute survey: https://aka.ms/GraphQLSupport
Justin Rackliffe commented
For me it is a lot around not having so many languages that sort of have the same goal. I will say the fragments model, types, resolver flexibility feel more like code than serial database queries which is my bias. The assumption is that the query is ad-hoc and you don't know what you need before you need it while also avoiding a lot of post processing of data.
Orens Xhagolli commented
GQL is very closely aligned with Kusto REST - the GQL spec is open source and quite far ahead from what Kusto has been doing in this space - it would be nice if the kusto team could provide a GQL server out of the box