arxiv.org
GraphQL Adoption and Challenges: Community-Driven Insights ...
Such a finding indicates the increasing difficulty of the GraphQL domain in the GraphQL community. Sri et al. (Vadlamani et al., 2021) confirms such difficulty of GraphQL in their recent study, which surveyed 38 Github employees who expressed that GraphQL was challenging to learn, time-consuming with limited knowledge-base resources, especially when compared to mature protocols such as REST. … Additionally, implementing REST queries became more challenging with complex endpoints and multiple parameters. Participants without experience found GraphQL easier to implement and understand (Brito and Valente, 2020). Wittern et al.’s empirical investigation of over 8K GraphQL schemas mined from GitHub suggests that most APIs have security issues that can be exploited using complex queries (Wittern et al., 2019).
Related Pain Points2件
Query complexity and performance degradation
7GraphQL queries can become increasingly complex as projects grow, with deeply nested queries and over-fetching of fields leading to poor performance, extensive database joins, and slow execution times. Query complexity assessment is difficult and clients can crater performance without guardrails.
GraphQL steep learning curve and debugging complexity
5GraphQL has a significant learning curve compared to REST APIs. Developers must learn schema definitions, resolvers, and query structures, and debugging is more complex. Studies show developers find GraphQL challenging and time-consuming to learn with limited knowledge-base resources.