Check out Graphiti.dev it shows how a few common sense conventions in REST give most or all the power of GraphQL. I think the phrase “comparing apples to orang

Check out Graphiti.dev it shows how a few common sense conventions in REST give most or all the power of GraphQL. I think the phrase “comparing apples to oranges” is a bit misleading in this context because it is normally used to imply that such comparison is impossible or not useful (i.e. a fruitless exercise, sorry, I couldn’t help it). But here there is a lot to compare. REST is built with the basic infrastructure of the web in mind so massive amounts of infrastructure like caching, error messaging do need to be rebuilt. GraphQL has some real benefits so a comprehensive comparison is worth it. Ultimately both are an api design to facilitate getting data. It’s sort of like comparing Postgres to MongoDB. Yes there are major differences but the expected use is to store data. Comparing is crucial. Either way. Have fun building cool stuff.