Skip to main content

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.16

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for backend.ai-appproxy-coordinator 26.4.16
File Size Uploaded Provenance Actions
backend_ai_appproxy_coordinator-26.4.16.tar.gz 89.4 kB Without provenance Details for backend_ai_appproxy_coordinator-26.4.16.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for backend.ai-appproxy-coordinator 26.4.16
File Interpreter ABI Platform Actions
backend_ai_appproxy_coordinator-26.4.16-py3-none-any.whl Python 3 none any Details for backend_ai_appproxy_coordinator-26.4.16-py3-none-any.whl

Total release size: 210.0 kB

Release files / backend_ai_appproxy_coordinator-26.4.16.tar.gz

Download URL backend_ai_appproxy_coordinator-26.4.16.tar.gz
Size 89.4 kB
Tags Source
SHA-256 checksum
How to use checksums
f2b50f23a3749fbf3695123101b0c2effeb59b32d347a639f2cb7cd2d91d05f8
BLAKE2b-256 checksum
How to use checksums
2a009406cd35cb92e111a7deee47878109019b43d44269616c0000f16004b13e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.2.0 CPython/3.13.18

Release files / backend_ai_appproxy_coordinator-26.4.16-py3-none-any.whl

Download URL backend_ai_appproxy_coordinator-26.4.16-py3-none-any.whl
Size 120.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cbf87da943d110747b968cfd4adf7795bfe210778bb4b850dbfd7d4a0349055b
BLAKE2b-256 checksum
How to use checksums
495acaaab125e1791fc662dcf598fe46b3d815c1eadf538888536d35f87ca880
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.2.0 CPython/3.13.18

Security for backend.ai-appproxy-coordinator 26.4.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

26.4.16 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page