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

Why is synchronous fan-out (one request calling many services) risky, and how do you reduce it?

Tags
#microservices#fan-out#latency#reliability#timeouts
Back to categoryPractice quiz

Answer

It increases latency (you wait for multiple calls), increases failure probability (one dependency failing breaks the whole request), and can amplify load. Reduce it by aggregating in a BFF/API Gateway, caching, using async/event-driven flows, and by setting timeouts + bulkheads so one slow dependency doesn’t stall everything.

Related questions

Microservices
Trace context propagation: what is the `traceparent` header and why should services forward it?
#microservices#observability#tracing
Microservices
Kafka ordering: what ordering guarantees do you get and how do you design for ordering?
#microservices#kafka#ordering
Microservices
REST vs gRPC for service-to-service calls: what are the key trade-offs?
#microservices#grpc#rest
Microservices
BFF (Backend for Frontend): what is it and when does it help?
#microservices#bff#api
Microservices
Multi-region microservices: what are the main benefits and the main pain points?
#microservices#multi-region#availability
Microservices
Distributed rate limiting: why is it harder than a simple in-memory counter?
#microservices#rate-limiting#redis