GraphQL is trying to put Menu Query Language on top of Structured Query Language and get the same full featured API. There are some use cases, but I think the use cases where a GraphQL API is the ONLY API is far and few between. The best solutions to me are when some endpoints of the API are done through GraphQL while others are RESTful in design still. The GraphQL spec will always be too restrictive to accomplish what developers want to do with it because of it's nature. Graph DBs like Dgraph/Neo4J and other db layers/services like EdgeDB/Hasura are making GraphQL popular which usually work beautifully for the ToDo apps but fall apart when you actually start to use them for production systems with more real world cases. And then we have newer layers coming along like Outcast which is trying to be a database with ONLY a GraphQL "query language" to do "everything" and you start to quickly see where the limitations are. the "QL" part of GraphQL is very deceiving to the novice developer who seem to be the main players in the GraphQL world.