Skip to content

DEP: Sidecar — Functionality impact & feature-parity inventory #10839

Open

Description

@tanmayv25

Parent: #10835
Status: stub — scope defined, detailed design pending.
Depends on: #10838 (destinations assume the contract surface).

Summary

Audit every current Python-wrapper responsibility and assign each a destination — unified backend, sidecar, or upstream engine — and enumerate the upstream API gaps each engine must close before the sidecar can claim feature parity.

Motivation

Parent #10835 gates sidecar graduation on parity gaps being identified and closed for the target workload. This DEP is that inventory and gate.

Proposal

To be detailed. Scope: per-engine (vLLM / SGLang / TRT-LLM) mapping tables and upstream API-gap lists, sourced from the Dynamo Sidecar Python Wrapper Functionality Report (see #10835 references). Representative parity areas (the report is the complete source): disaggregation handoff, KV events, load/capacity, logprobs / guided decoding / structured output, multimodal / embeddings, LoRA / weight-update / memory controls, diffusion, snapshot/checkpoint, and typed migration errors.

Activity

  1. added
    processCODEOWNER area -> @ai-dynamo/dynamo-process-codeowners
    on Jul 20, 2026
  2. 0z5a commented on Sep 18, 2026

    @0z5a

    @tanmayv25 I'd like to help drive this DEP. I can start with the vLLM feature-parity inventory: audit the current Python-wrapper responsibilities, map each one to unified backend / sidecar / upstream engine, and identify the remaining upstream API gaps against the #10838 contract.

    If that scope sounds good, I can post the initial vLLM mapping table here first and then extend the same structure to the other engines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    backend::sglangRelates to the sglang backendbackend::trtllmRelates to the trtllm backendbackend::vllmRelates to the vllm backenddep:draftDEP in draft statusenhancementNew feature or requestprocessCODEOWNER area -> @ai-dynamo/dynamo-process-codeownersrouterRelates to routing, KV-aware routing, etc.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions