GraphQL is a significantly enhanced REST API. The GraphQL website outlines some of the benefits over standard REST services:
When coded properly, multiple resources are handled simultaneously on the server, making it more performant. The challenge is that GraphQL requires:
A lot of this would be beyond many developers.
However, with a wizard or chatbot or other intelligent interface, it's possible to identify
Domino has the core CRUD / query API already there to intelligently map the schema to microfunctions to validate and process queries and mutations as a GraphQL server. The options available for GraphQL are not extensive, so I don't think the logic to convert the schema and associated meta-logic to actual code would not be too complex. The performance enhancements of gRPC / DQL may better handle parallel processing from a single GraphQL request.
Taking an innovative approach, the GraphiQL interface could be extended - for authorised users - to add / remove queries, mutations, objects, properties etc.
Of course this functionality could also be used to improve on the DAS APIs for mail, calendar and freebusy. That could provide a better performant Verse UI, as well as an API that pulls together multiple "mailboxes" into a single Verse UI for "team mailboxes", multiple calendar overlays etc.