I created a poll on Twitter here:<p>https://twitter.com/socializ3r/status/1527721872296665089<p>... go vote but would love to hear your thoughts on GraphQL.<p>I'm not going to bias the vote by giving my personal opinion but would love to hear yours.
Personaly, I'm fan of Cypher. We just published a blog post about different graph query languages few days ago.<p><a href="https://memgraph.com/blog/graph-database-query-languages-you-should-try" rel="nofollow">https://memgraph.com/blog/graph-database-query-languages-you...</a>
Did you know you can create polls here on HN instead of linking to Twitter?<p><a href="https://news.ycombinator.com/newpoll" rel="nofollow">https://news.ycombinator.com/newpoll</a>
When I first saw GraphQL, I was like "This is some overengineered shit that is going to be the next cargo cult"<p>Then I got actual exposure to it, and I think it's amazing in certain scenarios. You can easily make CRUD apps that allow a front-end to pick which database rows you want to update, and you create a metadata file that describes the database and applies permissions.<p>You get so many things for free, and the result is you have far less code to write and fewer bugs, especially around RBAC.<p>That being said, like many technologies, there will be people that try to use it for things it shouldn't be used for.
Compared to REST APIs, I like how it eliminates the coarse-grained vs. fine-grained decision for designing queries in APIs. You can just spec out the model and let the clients decide what they need.