3 ms·
GraphQL debates become a bit motte and bailey. Yes you can change anything you like and add in any behaviours you wish. But, each time you do that you move awa
by robertlagrant 5y ago
GraphQL debates become a bit motte and bailey.
Yes you can change anything you like and add in any behaviours you wish. But, each time you do that you move away from the promise that "you basically don't need backenders" or "if you're finding it tough, just use this tool!" The latter of which has appeared in this comment thread already more than once.
You can technically accomplish many things with GraphQL. But the effort to do so erodes the benefits promised.
- cersa8 5y agoEven though this is true, there can still be a lot of value in certain scenarios. For instance, this is why I use GraphQL strictly in my admin backends. Exposing the database almost verbatim through Postgraphile as an Express.js middleware. All data is now trivially accesible. Everything that requires custom resolvers or other complex customisations are handled over a Rest endpoint. I now have all the benefits of GraphQL without the complexities you face when moving into more edge case scenarios. In pretty much the same way I use Prisma ORM but raw queries for anything non trivial.
- robertlagrant 5y agoSure - anything that's basically generated dynamically off the database structure will work well, although you can also get auto-rest generators that would have a similar productivity effect.