This release is a pre-release and may not be stable for production use.
Backend.AI App Proxy Worker
Purpose
The App Proxy Worker is a high-performance reverse proxy that routes user traffic to compute session services (Jupyter, SSH, TensorBoard, etc.) running on agents. It receives routing information from the Coordinator and handles SSL/TLS termination, load balancing, and traffic forwarding.
Key Responsibilities
1. Traffic Proxying
- Proxy HTTP/HTTPS requests to session services
- Proxy WebSocket connections for interactive services
- Handle SSL/TLS termination
- Stream responses efficiently
2. Route Resolution
- Receive routing tables from Coordinator
- Resolve session services from URLs
- Cache routing information locally
- Update routes dynamically
3. Health Checking
- Monitor backend service health
- Detect failed services
- Report health status to Coordinator
- Handle service failover
Architecture
1. Traffic Proxy (Main)
Framework: aiohttp + custom reverse proxy
Port: 5050 (default, HTTPS)
Protocol: HTTP/HTTPS, WebSocket
Key Features:
HTTP/HTTPS Proxy
- Route user requests to session services
- URL Pattern:
https://<worker-domain>/<session-id>/<service-name>/...
WebSocket Proxy
- Interactive service communication (Jupyter Kernel, SSH, etc.)
- Real-time log streaming
Key Characteristics:
- SSL/TLS termination (Let's Encrypt auto-certificate)
- High-performance async proxy
- Connection pooling and reuse
- Streaming support (large file downloads)
- Sticky session support
- Auto-retry and failover
Processing Flow:
HTTP Proxy Flow
User → HTTPS Request → Worker (SSL termination)
↓
Parse URL (extract session_id, service_name)
↓
Lookup route from local cache
↓
Resolve backend address (agent:port)
↓
Proxy request to agent
↓
Stream response back to user
WebSocket Proxy Flow
User → WS Upgrade Request → Worker
↓
Establish WS connection to agent
↓
Bidirectional message forwarding
2. REST API (Management)
Framework: aiohttp (async HTTP server)
Port: 6040 (default, separate management port)
Key Features:
- Communication with Coordinator
- Health check endpoints
- Metrics exposure (Prometheus)
- Internal management (no external access)
Component Interaction
Traffic Proxy Flow:
User (Browser) → Worker (Port 5050) → Kernel (on Agent)
│
├─ SSL/TLS termination
├─ Route resolution
└─ Traffic proxying
Management Flow:
Coordinator → Worker REST API (Port 6040) → Route updates
Metadata
Release files for backend.ai-appproxy-worker 26.9.0rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| backend_ai_appproxy_worker-26.9.0rc1.tar.gz | 58.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| backend_ai_appproxy_worker-26.9.0rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 136.9 kB
Release files / backend_ai_appproxy_worker-26.9.0rc1.tar.gz
| Download URL | backend_ai_appproxy_worker-26.9.0rc1.tar.gz |
|---|---|
| Size | 58.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e7f43ba27b8de35c119ff0cddf0917ef1a01dd6dfa8b5aa2e9a41c85b559914
|
|
BLAKE2b-256 checksum How to use checksums |
6f6930632677bcba26ec068281c6050c6b47db233d0635171603f0cf35b0f54c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / backend_ai_appproxy_worker-26.9.0rc1-py3-none-any.whl
| Download URL | backend_ai_appproxy_worker-26.9.0rc1-py3-none-any.whl |
|---|---|
| Size | 78.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3bd37cc3959c09bc674fe8980c78b7d908259ece302b4a7485e08add67e9b719
|
|
BLAKE2b-256 checksum How to use checksums |
eb5bd86bf2f4b88ac51a29ad82446207c6240d13388fa3e620480b76ba6e8560
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
