A lot has to be reinvented with a GraphQL API. Errors, caching, rate limiting, timeouts, and so many other things are handled in many different ways by GraphQL API providers at the moment
📕Marc-Andre Giroux | Production Ready GraphQL
Josh BeckmanFiled under:
Same Source
- All in all, I don’t think service communication is the sweet spot f...
- GraphQL is purposefully transport/protocol agnostic. Nothing is sto...
- build a GraphQL API server that is resolved by many underlying serv...
- Airbnb’s approach of wiring up different schemas together to form t...
- My advice would be for GraphQL APIs to rely on conventions as much ...
- The trade-off, though, is that a uniform interface degrades efficie...
- We can often categorize APIs in three broad categories: Private API...
- View all