4 ms·
Not a fan of GraphQL (the problems mentioned in the post are very real), but GraphQL specification does not say anything about the DB design / queries. It is st
by rockyj 2y ago
Not a fan of GraphQL (the problems mentioned in the post are very real), but GraphQL specification does not say anything about the DB design / queries. It is still an API layer and you are free to model it in any way you want.
- discreteevent 2y agoIndeed, from one of the authors of graphQL on this very forum: "That would be one way to implement the system in a DB-centric way. However we believe that intermediate application code is pretty critical to any GraphQL implementation." [1] "GraphQL is a client-server dance that needs server-side capabilities, not just CRUD semantics." [2] [1] https://news.ycombinator.com/item?id=9879870 https://news.ycombinator.com/item?id=9879870 [2] https://news.ycombinator.com/item?id=14351800 https://news.ycombinator.com/item?id=14351800
- dventimi 2y agoI do not share that author's belief about application code.