I'm investigating adopting GraphQL for our system but our system requires a ton of side effect triggers including but not limited to: zip/unzip files, req other back end services, put files in a caching layer, parse those files on req, etc. With REST this is obvious since you can place this logic in controllers and off you go. I peeked through the graphql docs and didn't see anything that would help with this.Would we need to keep some REST endpoints around for all these side effect use cases? FWIW I'm a front end guy so I could be missing something obvious
Submitted January 24, 2020 at 03:00PM by Peechez
No comments:
Post a Comment