Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Microservices
Microservicesmedium

Synchronous vs asynchronous communication — what’s the trade-off?

Tags
#communication#http#messaging#eventual-consistency
Back to categoryPractice quiz

Answer

Sync calls (HTTP/gRPC) are simpler and give immediate response, but create tight coupling and can cascade failures. Async messaging improves decoupling and resilience, but adds eventual consistency and operational complexity (queues, retries, ordering).

Related questions

Microservices
At-least-once delivery: how do you avoid duplicate side effects in a consumer?
#idempotency#deduplication#messaging
Microservices
What is a schema registry and why is it useful for events?
#schema-registry#events#compatibility
Microservices
Why do consumers need to be idempotent in event-driven systems?
#idempotency#messaging
#retries
Microservices
How to handle data consistency in microservices (saga, outbox)?
#saga#outbox#consistency
Microservices
How do microservices communicate? Synchronous vs asynchronous.
#communication#rest#grpc
Spring
WebClient vs RestTemplate: which should you use and why?
#spring#webclient#resttemplate