api design whens rest the wrong choice

hey everyone, ive been thinking a lot about API design lately, especially with the rise of alternatives like gRPC and GraphQL. We often default to REST because its familiar and well-understood, but are there specific scenarios where it's actually the less optimal choice? For instance, for high-throughput, low-latency internal microservices, or when dealing with complex, deeply nested data structures? What are your experiences with choosing between REST, gRPC, GraphQL, or other patterns? Lets discuss the trade-offs and figure out when to deviate from the RESTful path.