Backend.AI App Proxy Coordinator
Purpose
The App Proxy Coordinator manages routing information for App Proxy Workers, coordinates worker instances, and handles service port mappings for compute session services (Jupyter, SSH, TensorBoard, etc.).
Key Responsibilities
1. Worker Management
- Register and track App Proxy Worker instances
- Monitor worker health and availability
- Distribute routing information to workers
- Handle worker failover
2. Route Management
- Manage service port mappings (session → service → port)
- Update routing tables dynamically
- Propagate route changes to workers
- Handle route conflicts and resolution
3. Service Discovery
- Maintain service registry
- Provide route lookup for workers
- Update routes when sessions change
- Clean up routes for terminated sessions
Entry Points
App Proxy Coordinator has 1 entry point to receive and process requests.
1. REST API
Framework: aiohttp (async HTTP server)
Port: 6030 (default)
Primary Purpose:
- Worker management (registration, monitoring)
- Routing information management (session-to-service port mapping)
Key Features:
- HTTP/HTTPS-based communication
- Centralized service routing information management
- Real-time route updates
- Persistent routing information storage in PostgreSQL
Processing Flow:
Worker Registration Flow
Worker → POST /workers/register → Coordinator
↓
Register worker in DB
↓
Return worker ID and routes
Route Creation Flow
Manager → POST /routes → Coordinator
↓
Store route in DB
↓
Notify all workers
↓
Workers update local routing table
Integrated Architecture:
┌──────────────┐
│ Manager │
│ │
└──────┬───────┘
│ Route Management (REST)
▼
┌─────────────────────────────────────┐
│ App Proxy Coordinator (Port 6030) │
│ - Worker registration │
│ - Route management │
│ - Service port mapping │
│ - Route propagation │
└─────────┬───────────────────────────┘
│
▼ Worker Registration & Route Updates
┌─────┴─────┬─────────┬─────────┐
▼ ▼ ▼ ▼
┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐
│Worker 1│ │Worker 2│ │Worker 3│ │Worker N│
└────────┘ └────────┘ └────────┘ └────────┘
Metadata
Release files for backend.ai-appproxy-coordinator 26.4.13
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_coordinator-26.4.13.tar.gz | 88.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| backend_ai_appproxy_coordinator-26.4.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 208.1 kB
Release files / backend_ai_appproxy_coordinator-26.4.13.tar.gz
| Download URL | backend_ai_appproxy_coordinator-26.4.13.tar.gz |
|---|---|
| Size | 88.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9928677bccce558dc067cf8cff999dc2d0821d734afb2122b58231f8eeb1c997
|
|
BLAKE2b-256 checksum How to use checksums |
0bdd7b2a4bc3a0b6d67cbcdc0d276d3b88cb1a77c50a139d26ff8bc14a0eba3a
|
| 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_coordinator-26.4.13-py3-none-any.whl
| Download URL | backend_ai_appproxy_coordinator-26.4.13-py3-none-any.whl |
|---|---|
| Size | 119.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb7a3d6041ff1bdfe82b9e4602570dfc5737cf39e893a74ac5054face7f9d084
|
|
BLAKE2b-256 checksum How to use checksums |
e5df439058fb0d41e846d51272f7f37a00bf2ccba857a94d2688b43a2ef21c4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
