| I personally think it is amazing and relevant. These two videos are worth watching for the reasons: in short, it's a great way to aggregate legacy backend services. And, your client data shapes are much better, and this makes a difference when optimizing your server side (without knowing how your clients use the data, you can't really optimize, which REST doesn't tell you). https://www.youtube.com/watch?v=H8YnVk2vhzg https://www.youtube.com/watch?v=zVNrqo9XGOs But, the reality is that even the biggest providers of public APIs, GitHub being the biggest example, have major holes in their offerings. For example, you can't yet make commit mutations in their API, which means you can't edit git data using their graphql API, though you can edit GitHub data... (My O'Reilly book is still relevant for this reason: https://buildingtoolswithgithub.teddyhyde.io/) Graphql is not always the best fit, but it is really a powerful idea. In the same way that people suggest you learn a new language each year even if you don't necessarily switch to using it full time, learning graphql will make you really think through how you access APIs. |