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."

Neither answer explains which product requirement supports the choice or which costs 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 resource needs. I would consider GraphQL for several first-party clients whose scre