5 exercises on microservices communication vocabulary.
0 / 5 completed
1 / 5
What is synchronous communication between microservices?
Synchronous communication: the calling service blocks until it receives a response. REST over HTTP and gRPC are common examples. It is simple but couples availability: if the called service is down, the call fails immediately.
2 / 5
What is the main benefit of asynchronous messaging between microservices?
Asynchronous messaging: the producer publishes a message and continues without waiting. The consumer processes it at its own pace. This decouples availability and smooths traffic spikes, at the cost of eventual consistency.
3 / 5
What is a service mesh in microservices communication?
Service mesh: a dedicated infrastructure layer that intercepts all inter-service traffic via sidecar proxies, providing observability, retries, mutual TLS, and load balancing without requiring application code changes.
4 / 5
Why can chatty communication (many fine-grained calls) harm microservices performance?
Chatty communication: each network hop adds latency and the risk of failure. If service A calls B which calls C which calls D, small individual delays compound. API composition, BFF patterns, and batching reduce unnecessary round trips.
5 / 5
What does idempotent messaging guarantee in a microservices event stream?
Idempotent messaging: at-least-once delivery means duplicates are possible. Designing consumers to be idempotent (e.g., using a message ID to detect duplicates) ensures repeated processing does not corrupt state.