graphQL

1 min read, 69 words graphQL

The good the bad and the ugly

Pros

• Solves the @client problem fo overfetching and underfetching
• @server spegghati API endpoints paths, less maintenance

Cons

• Caching mechanism is required @client
• graphQL requests are >> in size than normal requests
• Extra code and work on both @client and @server in kbs in comparision to traditional REST path

Subscribe to our Newsletter

If you like my work and think it was helpful kindly support my work