REST vs gRPC vs GraphQL

The interviewer looks at the operations you have drawn and asks:

"Would GraphQL be better here?"

Two answers are common. "Yes, GraphQL is flexible and avoids over-fetching." "No, REST is simpler and more standard."

Both are unpriced opinions. One praises an alternative and the other praises the default, and neither names the product fact that settles the choice or the cost the team accepts.

A design answer starts differently:

"It depends on who calls this API, and whether the clients need materially different connected field sets. I would keep REST for a public API with stable resourc