📡 Sync vs Async Communication
Microservices Communication Patterns — Complete Visual Guide
🧠 Mental Model: Phone Call vs Email
📞 SYNC = Phone Call (wait, immediate, both available)
✉️ ASYNC = Email (no wait, eventual, independent)
🎯 Think of calling vs emailing — the same principles apply to microservices!
📞 SYNC
Request-Response Pattern
┌────────┐ ┌────────┐
│ Client │────►│ Server │
└────────┘ └────────┘
▲ │
└──────Wait─────┘
⏱️ Client blocks until response
┌────────┐ ┌────────┐
│ Client │────►│ Server │
└────────┘ └────────┘
▲ │
└──────Wait─────┘
⏱️ Client blocks until response
REST API / gRPC Example
GET /api/orders/123 → 200 OK { "status": "completed" }
REST
gRPC
GraphQL
WebSocket
✉️ ASYNC
Event-Driven Pattern
┌────────┐ ┌──────────┐ ┌──────────┐
│Producer│────►│ Message │────►│ Consumer │
└────────┘ │ Broker │ └──────────┘
└──────────┘
✅ Producer continues immediately
┌────────┐ ┌──────────┐ ┌──────────┐
│Producer│────►│ Message │────►│ Consumer │
└────────┘ │ Broker │ └──────────┘
└──────────┘
✅ Producer continues immediately
Kafka / RabbitMQ Example
topic: "order-events" → partition 0 → consumer group
Kafka
RabbitMQ
SQS
Redis
| Factor | SYNC | ASYNC |
|---|---|---|
| Latency | 🟢 Low (immediate) | 🟡 Higher (event delay) |
| Coupling | 🔴 Tight | 🟢 Loose |
| Scalability | 🟡 Limited (thread bound) | 🟢 High (decoupled) |
| Consistency | 🟢 Strong | 🟡 Eventual |
| Debugging | 🟢 Easy | 🔴 Hard (distributed) |
| Complexity | 🟢 Simple | 🟡 Complex |
| Best For | User-facing, real-time | Background, analytics |
🌳 Decision Tree: Which One to Use?
Q1: Immediate response required?
├─ YES → USE SYNC
└─ NO → Continue
Q2: User-facing critical path?
├─ YES → USE SYNC
└─ NO → Continue
Q3: Can processing be delayed?
├─ YES → USE ASYNC
└─ NO → USE SYNC
├─ YES → USE SYNC
└─ NO → Continue
Q2: User-facing critical path?
├─ YES → USE SYNC
└─ NO → Continue
Q3: Can processing be delayed?
├─ YES → USE ASYNC
└─ NO → USE SYNC
🔄 The Hybrid Pattern: Best of Both Worlds
Use SYNC for critical path, ASYNC for side effects
🛒 User Request
→
📦 Order Service
→
💳 Payment Service
→
📊 Inventory Check
→
✅ Response to User
⬇️ ⬇️ ⬇️
📧 Email Service
📦 Shipping Service
📈 Analytics Service
🔔 Notification Service
⚡ These run in background — user doesn't wait!
🎯 4 Golden Rules
1️⃣
User clicks? → SYNC
2️⃣
Notification? → ASYNC
3️⃣
Immediate result? → SYNC
4️⃣
High scale? → ASYNC
"Sync for critical path, Async for side effects"
🎯 One-Line Summary
"SYNC for immediate user-facing responses, ASYNC for everything that can wait."
"SYNC for immediate user-facing responses, ASYNC for everything that can wait."