Networking

Shared Platform Network

The Arya Banking platform relies on a single, shared Docker bridge network named arya-banking-net.

Role of arya-banking-net

• Isolation: All platform containers are restricted to this network, preventing accidental exposure of internal services.
• Service Discovery: Eureka and the Config Server use container hostnames (e.g., arya-banking-service-registry) to communicate within the bridge.
• Inter-service Traffic: Non-public traffic (e.g., Kafka to microservices) flows entirely through this network.

Port Mapping Reference

The platform uses consistent port mapping (Host → Container) to maintain predictability during development.

Mixed Docker + Local Connectivity

When the platform stack (Service Registry, Config Server, API Gateway) runs in Docker but business services (User, Auth, Admin) run locally via Maven, the business services must register with Eureka using an address reachable from Docker containers. The shared config in arya-banking-configs sets:

eureka:
  instance:
    hostname: host.docker.internal

This ensures locally-run services advertise themselves as host.docker.internal:<port>, which the Docker gateway container can reach.

Traffic Flow

1. North-South Traffic: Enters through Port 8085 (API Gateway) and is routed to individual services on 8086-8089.
2. East-West Traffic: Inter-service Feign calls bypass the Gateway and communicate directly via container hostnames on their respective host ports (configured via Eureka).