Microservices communication pattern

Navrhni communication pattern pro microservices:\n\n**Services:**\n1. [SERVICE 1] - responsibilities\n2. [SERVICE 2] - responsibilities\n3. [SERVICE 3] - responsibilities\n\n**Communication Needs:**\n[SCENARIOS - např. Service A needs data from Service B, async notifications]\n\n**Pattern Type:**\n[SYNCHRONOUS/ASYNCHRONOUS/HYBRID]\n\n**Options:**\n1. **Sync:** REST, gRPC\n2. **Async:** Message queue (RabbitMQ, Kafka), Event bus\n\n**Design:**\n- API contracts (proto/OpenAPI)\n- Error handling & retries\n- Circuit breaker\n- Service discovery\n- Authentication (service-to-service)\n- Monitoring & tracing\n\n**Provide:**\n- Architecture diagram (text description)\n- Implementation examples\n- Pros/cons of chosen pattern\n- Failure scenarios\n\nStack: [STACK].