Migrating to GraphQL: A Practical Assessment

Brito, Gleison; Mombach, Thaís; Valente, M.

doi:10.1109/saner.2019.8667986

Cited by 41 publications

(30 citation statements)

References 27 publications

(46 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The remaining academic literature on GraphQL focuses on the challenges of creating a GraphQL API. Several research teams have described their experiences exposing a GraphQL API or migrating existing APIs to GraphQL [16,27,28]. Others have described automatic techniques for migration [31] and testing [26].…”

Section: Related Workmentioning

confidence: 99%

An Empirical Study of GraphQL Schemas

Wittern

Cha

Davis

et al. 2019

Service-Oriented Computing

View full text Add to dashboard Cite

GraphQL is a query language for APIs and a runtime to execute queries. Using GraphQL queries, clients define precisely what data they wish to retrieve or mutate on a server, leading to fewer round trips and reduced response sizes. Although interest in GraphQL is on the rise, with increasing adoption at major organizations, little is known about what GraphQL interfaces look like in practice. This lack of knowledge makes it hard for providers to understand what practices promote idiomatic, easy-to-use APIs, and what pitfalls to avoid. To address this gap, we study the design of GraphQL interfaces in practice by analyzing their schemas -the descriptions of their exposed data types and the possible operations on the underlying data. We base our study on two novel corpuses of GraphQL schemas, one of 16 commercial GraphQL schemas and the other of 8,399 GraphQL schemas mined from GitHub projects. We make available to other researchers those schemas mined from GitHub whose licenses permit redistribution. We also make available the scripts to mine the whole corpus. Using the two corpuses, we characterize the size of schemas and their use of GraphQL features and assess the use of both prescribed and organic naming conventions. We also report that a majority of APIs are susceptible to denial of service through complex queries, posing real security risks previously discussed only in theory. We also assess ways in which GraphQL APIs attempt to address these concerns.

show abstract

Section: Related Workmentioning

confidence: 99%

An Empirical Study of GraphQL Schemas

Wittern

Cha

Davis

et al. 2019

Service-Oriented Computing

View full text Add to dashboard Cite

show abstract

“…Another example of a middleware change is the transition from RESTful APIs to GraphQL. GraphQL addresses some of the over-fetching and underfetching drawbacks found in RESTful APIs [1,9]. Wittern et al [13] introduce OASGraph, which uses the OpenAPI IDL to wrap a GraphQL wrapper around REST-like interfaces.…”

Section: Related Workmentioning

confidence: 99%

Apodini

Schmiedmayer

2020

Proceedings of the 21st International Middleware Conference Doctoral Symposium

View full text Add to dashboard Cite

“…GraphQL has seen increasing adoption because it offers three advantages over other web API paradigms. First, GraphQL reduces network traffic and server processing because users can express their data requirements in a single query [29]. Second, it simplifies API maintenance and evolution by reducing the number of service endpoints [37].…”

Section: Introductionmentioning

confidence: 99%