To design a microservice that needs data from 3 other services without tight coupling, I would follow these principles: 1️⃣ API Composition / Aggregator Pattern Introduce an orchestrator or aggregator service that calls the 3 dependent services. The consumer service interacts with only one API, not all 3 services directly. This keeps the core service clean and loosely coupled. 2️⃣ Asynchronous Communication (Event-Driven) Use events (Kafka/RabbitMQ) where possible instead of synchronous REST cal

Service Design 101

SOA vs. Microservices: What’s the Difference? | IBM

Challenges of Microservices & When To Avoid Them