almost never, when you at the point where your REST looks like a mess - graphql would only make it worse when your REST is still manageable - graphql doesn't

almost never, when you at the point where your REST looks like a mess - graphql would only make it worse when your REST is still manageable - graphql doesn't bring anything radically new or intrinsically valuable to the table Probably the only good fit is when you actually fetching a lot of _graph_ data.