You are designing a microservices architecture for a new application that will be deployed on Cloud Run. The application requires high-throughput communication between the internal microservices. You

Question

Options

• AConfigure the Cloud Run service to use HTTP/2. Implement gRPC for communication between
• BImplement the microservices with the REST API communication protocol. Use Apigee with rate-
• CUse SOAP to build the microservices API, and use XML as the data format for communication
• DUse HTTP REST to communicate across the microservices. Implement pagination and add

• A
  80% (33)
• B
  12% (5)
• C
  5% (2)
• D
  2% (1)

Explanation

gRPC over HTTP/2 is the optimal choice for high-throughput, low-latency internal microservice communication. gRPC uses Protocol Buffers (a compact binary serialization format), supports bidirectional streaming, multiplexes multiple requests over a single connection, and eliminates HTTP/1.1 head-of-line blocking. Cloud Run natively supports HTTP/2, making this configuration straightforward. Option B (REST with Apigee) adds an API gateway layer that introduces latency and overhead - Apigee is better suited for external-facing APIs. Option C (SOAP/XML) is verbose, computationally expensive to serialize/deserialize, and an outdated protocol not suited for high-throughput microservices. Option D (HTTP REST with pagination) is a viable pattern for external APIs but adds unnecessary latency compared to gRPC for internal service-to-service calls.

No community discussion yet for this question.