5 ms·
I haven’t left GraphQL myself, but after seeing what’s necessary to expose GraphQL for consumption, it’s very clearly an attractive waste of time. After having
by andrewmcwatters 7y ago
I haven’t left GraphQL myself, but after seeing what’s necessary to expose GraphQL for consumption, it’s very clearly an attractive waste of time.
After having worked on a codebase with it, I would prefer RESTful endpoints backed by RDBMS or document stores instead.
- charlie0077 7y agoI feel the same pain and end up built a library to try to solve it. https://github.com/charlie0077/graphql-server-crud https://github.com/charlie0077/graphql-server-crud
- tsuberim 7y agoHey, I created this thing: https://graph-4d1ec.firebaseapp.com/ https://graph-4d1ec.firebaseapp.com/