Networking & Port Configuration
Relevant source files
The following files were used as context for generating this wiki page:
Introduction
The Aether-X Ultimate platform utilizes a microservices architecture where components communicate over a dedicated virtual network. Networking is structured to provide clear separation between public-facing gateways and internal backend services, ensuring scalable and secure data flow across content generation, AI modeling, and security modules. Sources: README.md:10-18, docker-compose.yml:158-160
This system relies on standardized port assignments to facilitate service discovery and inter-service communication. Traffic is primarily routed through an API Gateway or Nginx Load Balancer, which acts as the entry point for external client requests before forwarding them to the appropriate microservice. Sources: services/api-gateway/app.py:14-22, docker-compose.yml:144-156
Architecture & Data Flow
Request Routing Logic
The network architecture is designed around an API Gateway that proxies requests to internal services based on the URL path. Backend services are not directly exposed to the public internet but are accessible via the gateway on the aether-x-network. Sources: docker-compose.yml:111-125, services/api-gateway/app.py:61-90
The diagram above illustrates the flow of a request from an external client through the load balancing layer to the internal microservices and their respective data stores. Sources: docker-compose.yml:8-156
Internal Service Endpoints
Within the internal network, services use specific DNS names mapped to their functional roles. This is particularly evident in the API Gateway's service mapping and Kubernetes service definitions. Sources: services/api-gateway/app.py:15-22, k8s/deployment.yaml:37-45
| Service Name | Internal URL (Docker/K8s) | Internal Port | External Port (Dev) |
|---|---|---|---|
| Text Generation | http://text-generation-service:8000 | 8000 | 8000 |
| Image Generation | http://image-generation-service:8001 | 8001 | 8001 |
| Video Generation | http://video-generation-service:8002 | 8002 | 8002 |
| AI Models | http://ai-models-service:8003 | 8003 | 8003 |
| No-Code Dev | http://no-code-development-service:8004 | 8004 | 8004 |
| Security | http://security-service:8005 | 8005 | 8005 |
| Data Processing | http://data-processing-service:8006 | 8006 | 8006 |
| API Gateway | http://api-gateway-service:80 | 80 | 80 |
Sources: README.md:11-18, services/api-gateway/app.py:15-22, setup-dev.sh:88-109
Infrastructure & Database Networking
Database Connectivity
The infrastructure layer defines a suite of databases accessible to the microservices. These services are grouped within the aether-x-network bridge. Sources: infrastructure/databases/docker-compose.yml:171-173
Messaging & Monitoring Ports
The platform utilizes Apache Kafka for message queuing and a Prometheus/Grafana stack for monitoring. These components occupy a specific range of ports for management and data ingestion. Sources: infrastructure/databases/docker-compose.yml:95-115, docker-compose.yml:128-142
| Component | Port | Purpose |
|---|---|---|
| Kafka | 9092 | Message Broker Traffic |
| Zookeeper | 2181 | Distributed Coordination |
| Schema Registry | 8081 | Avro/JSON Schema Management |
| Prometheus | 9090 | Metrics Collection |
| Grafana | 3001 | Metrics Visualization |
| Kibana | 5601 | Log Analysis |
Sources: setup-dev.sh:114-126, infrastructure/databases/docker-compose.yml:104-166
Kubernetes Network Configuration
In production environments, networking is managed via Kubernetes Services and Ingress controllers. Services are typically defined as ClusterIP for internal communication, while the API Gateway uses a LoadBalancer type. Sources: k8s/deployment.yaml:37-45, k8s/api-gateway.yaml:1-13
Ingress Rules
The aether-x-ingress manages external access to the cluster services, providing path-based routing and SSL termination. Sources: k8s/deployment.yaml:236-267
Sources: k8s/deployment.yaml:252-267
Network Security Policies
The configuration includes rate limiting annotations at the Ingress level to protect the internal network from saturation. For example, a rate limit of 100 requests per minute is applied to the primary host. Sources: k8s/deployment.yaml:241-244
Summary
The networking and port configuration of Aether-X Ultimate ensures a structured environment where each microservice operates on a dedicated port (8000-8006). By utilizing a centralized API Gateway and Nginx load balancer, the system achieves a decoupled architecture that facilitates independent scaling and secure internal communication via the aether-x-network. Sources: README.md:10-18, docker-compose.yml:158-160