The trade-off, though, is that a uniform interface degrades efficiency, since information is transferred in a standardized form rather than one which is specific to an application’s needs. The REST interface is designed to be efficient for large-grain hypermedia data transfer, optimizing for the common case of the Web, but resulting in an interface that is not optimal for other forms of architectural interaction
Production Ready GraphQL
from Marc-Andre Giroux 📕
Filed 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 ...
- A lot has to be reinvented with a GraphQL API. Errors, caching, rat...
- We can often categorize APIs in three broad categories: Private API...
- View all
Related Notes
- discipline doesn’t scale, and if you want people to use good practi...from Fernando Borretti
- we are creating more data than we can manage. The primary output o...from johnnydecimal.com
- Maybe the devices that we ended up with are too flat, too homogenou...from Kyle Chayka
- Sometimes people use "respect" to mean "treating som...from kottke.org
- I recommend that teams receiving executive feedback try to “extract...from Irrational Exuberance
- Syntax coloring isn't useless, it is childish, like training wh...from Douglas Crockford
- Text inputs have no affordances When I go up the mountain to ask t...from wattenberger.com
- Forcing functions are the extreme case of strong constraints that c...from Don Norman