transform-service-communication

What problem does it solve?

Replaces direct service calls with config-driven ServiceClient usage to ensure URLs come from config, enabling consistent authentication, correlation, and resilience patterns across services.

Core Features & Use Cases

• Config-driven endpoints: fetch service URLs from centralized config to prevent hardcoding.
• Resilience: circuit breakers and exponential backoff retries for failed inter-service calls.
• Secure service-to-service communication: JWT-based authentication and tenant scope headers.
• Observability: correlation IDs logged with each request for traceability.
• Use case: refactor a user-management or auth service call to rely on ServiceClient.

Quick Start

Refactor a direct service call to a ServiceClient initialized with a config URL and appropriate headers.