|
|
|
|
|
|
by rwieruch
2525 days ago
|
|
|
1) I think GraphQL is more relevant than ever. Facebook ran into the same problems like Netflix, Airbnb and Twitter and thus came up with GraphQL [0]. 2) The most popular one I know is GitHub's GraphQL API [1]. I made the difficult decision to rely on their API to teach GraphQL in my free book [2]. So far, there were no breaking changes for me and people love it to learn GraphQL from a client's perspective. 3)I would use it if I want to have no under-/overfetching, declarative data fetching, microservice API aggregation, ... [3] 4) Using it in personal projects and one client of mine is using it in one application to aggregate multiple microservices (each one speaking GraphQL) into one GraphQL API gateway. So far, everything works like expected. We didn't hit any rate limiting and caching issues because of the N+1 problem yet. But we are prepared for them :) [0] https://www.youtube.com/watch?v=783ccP__No8 [1] https://developer.github.com/v4/ [2] https://www.robinwieruch.de/the-road-to-graphql-book/ [3] https://www.robinwieruch.de/why-graphql-advantages-disadvant... |
|
|