I really hate these bland, barely actionable advices with no examples, created for SEO purposes. Nobody knows how to measure the "complexity" and "evolvability

I really hate these bland, barely actionable advices with no examples, created for SEO purposes. Nobody knows how to measure the "complexity" and "evolvability" of the API and where exactly is the threshold that justifies going from REST to GraphQL. So here's my opinionated alternative: Use REST everywhere, unless you can justify the exception. A good exception is when you don't know the audience and use cases for your API. E.g. if you have hundreds of different apps using the same API and you have no idea how they are going to use it. You know who does it? Facebook. If you're just dogfooding an API for your website, you don't need GraphQL. If you need one service to talk to another, you don't need GraphQL.