GraphQL vs REST: API Design Best Practices For Long-Running Operationsby@growthatwundergraph
506 reads
506 reads

GraphQL vs REST: API Design Best Practices For Long-Running Operations

by WunderGraph 11mMay 6th, 2022
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

A GraphQL Schema makes it easier to reason about long-running operations from a developer's perspective. The REST approach on the other hand is a lot easier to implement. WunderGraph puts a GraphQL RPC layer in front of all your APIs (GraphQL, REST, Databases, etc.) Combined with a generated client, we make using APIs as easy as possible, highly secure and performant. A better approach would be to design our API as an asynchronous API. Instead of returning a response immediately, we should return a response with a unique identifier.

People Mentioned

Mention Thumbnail

Company Mentioned

Mention Thumbnail
featured image - GraphQL vs REST: API Design Best Practices For Long-Running Operations
WunderGraph  HackerNoon profile picture
WunderGraph

WunderGraph

@growthatwundergraph

Declaratively turn your services, databases and 3rd party APIs into a secure, unified, and extensible API.

Learn More
LEARN MORE ABOUT @GROWTHATWUNDERGRAPH'S
EXPERTISE AND PLACE ON THE INTERNET.

Share Your Thoughts

About Author

WunderGraph  HackerNoon profile picture
Declaratively turn your services, databases and 3rd party APIs into a secure, unified, and extensible API.

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite
Also published here
L O A D I N G
. . . comments & more!