re: Design an easy to use and flexible REST API VIEW POST


As someone who has been working with GraphQL a lot, this hurts my eyes and my head. I would recommend in this case that a GraphQL API is the better way to go.


I agree, that is what make it a better choice, to be able to select exactly what data to fetch. Plus the fact that you define what you get is very appealing. I like the concept a lot, I just do not dare to make the leap from here because I still work a lot with REST or RPC interfaces. Maybe some day 😁

Code of Conduct Report abuse