Tommaso Marcelli
Jul 25, 2017 · 1 min read

GraphQL is indeed intriguing but your article makes me think it might be wise to still wait for a while before adopting it in real projects. As pointed out by other readers, your depiction of REST APIs is a bit too simplistic. For instance, getting a record with its associations takes exactly one line of code in ActiveRecord (Ruby on Rails), and you can be sure you don’t get an N+1 problem. The thing that concerns me the most is that GraphQL can be very convenient from a front-end development point of view but looks really black box with respect to the DB implementation. Everything I read about it points out the advantages on the client side but I don’t think I’d be comfortable having no control whatsoever over the queries which are executed on my DB(s).