We should think about using GraphQL instead of REST for new APIs when we have complex data needs, or when we want clients to request exactly what they need.

Okay, so we're kicking off a new project, and it'll have a bunch of client apps needing data. I'm torn between our usual RESTful API or checking out GraphQL this time. For anyone who's actually made that jump or really looked into both, when does GraphQL actually become the obvious choice? I'm curious about the big signs that it's a better fit than REST, especially when you think about how flexible it is for different clients and handling data needs that keep changing, all without constantly tweaking the backend. Are there particular data setups or client demands that just scream