Where is gRPC useful? gPRC is synchronous request-response. So the question really is, where should use synchronous request-response?

DiscDot provides insights into distributed systems, cloud computing, and scalable architectures, offering articles and best practices for designing and implementing resilient and scalable distributed systems. By exploring DiscDot's curated content, developers can learn about distributed data storage, fault-tolerance mechanisms, and distributed computing frameworks for building highly available and performant applications. Whether you're architecting microservices, deploying containerized workloads, or managing distributed databases, DiscDot offers  insights and practical guidance to help you tackle the challenges of building distributed systems.

Discover .NET

GRPC is the standard for communication between services without giving any real reason. Queries and performing UI/ViewModel Composition are naturally request-response and would be a good fit for gRPC. Service-to-service communication using blocking RPC calls can lead to a nightmare of coupling and terrible reliability.

Where should you use gRPC? And where NOT!