3 ms·
I think the issue is more with framing. GraphQL is excellent for when you’re implementing an external facing api or a data focused api. Internal APIs where yo
by AlphaSite 7y ago
I think the issue is more with framing.
GraphQL is excellent for when you’re implementing an external facing api or a data focused api.
Internal APIs where you also own the client or have operation (side effect) heavy clients. These imo would be far better suited to REST.
- kumarvvr 7y agoInteresting, I was thinking the complete opposite. GraphQL for internal api or single client api, while a REST api for external consumers. Internal graphql api can be iterated and broken faster, adapting it for internal use as the app grows, while an external REST api would be more carefully generated and thoroughly documented.
- kumarvvr 7y agoIn addition to my other reply, it serves well to finely granularize an external facing API so that consumers can mix and match to their requirement. This granularity is best accomplished by a REST Api.