3 ms·
Whether or not your system intentionally ended up with this architecture, GraphQL provides a unified way of fetching the data. You'll still have to implement th
by JMTQp8lwXL 7y ago
Whether or not your system intentionally ended up with this architecture, GraphQL provides a unified way of fetching the data. You'll still have to implement the details of how to fetch from the various services, but it gives people who just want read access to everything a clean abstraction for doing so.
- benwaffle 7y agoREST can do the exact same thing.
- nathankunicki 7y agoWith less flexibility, and more round trips.
- jsjohnst 7y ago> With less flexibility, and more round trips That all depends on the API.
- nathankunicki 7y agoSure - but if you ever want it to be as flexible as GQL, you need to implement...a query language?
- MadWombat 7y agoI am not sure about that. Both RESTful APIs and GraphQL APIs need to be designed and flexibility is basicaly a measure of how good your API design is. I don't see how GraphQL is intrinsically more flexible.
- adamc 7y agoIt's nice to have a clean abstraction, but if the various services are on tables in different databases, things like joins get much more expensive, no? Performance is important.