litellm/docs/architecture
narmstrong-berry 624a80b59b
Some checks failed
LiteLLM Rust DB / db-queries (push) Has been cancelled
LiteLLM Rust / rust-lint (push) Has been cancelled
LiteLLM Rust / rust-test (push) Has been cancelled
LiteLLM Rust / rust-wheel (push) Has been cancelled
Terraform Modules / fmt, validate, test (aws) (push) Has been cancelled
Terraform Modules / fmt, validate, test (gcp) (push) Has been cancelled
docs(router): concept-led architecture docs for the Rust router core
Diataxis-style docs under docs/architecture/router describing the router as the Rust core
litellm-router-core runs it on nate_router_step6_rust_core_v2: deployments and model groups,
name resolution, teams and access, the filter chain, strategies, routing groups and
sub-routers, retries, fallbacks and cooldowns, shared state, and the core and its host.

Claude-Session: https://claude.ai/code/session_013FDwtmdtKxVdjQX8WK43iK
2026-11-05 13:53:56 -08:00
..
img docs(router): concept-led architecture docs for the Rust router core 2026-11-05 13:53:56 -08:00
router docs(router): concept-led architecture docs for the Rust router core 2026-11-05 13:53:56 -08:00
README.md docs(router): concept-led architecture docs for the Rust router core 2026-11-05 13:53:56 -08:00

Architecture

This folder explains how the parts of LiteLLM work inside, for the people who change them. It covers one component so far, the router. More will follow as the Rust migration moves each module behind a public interface and into Rust.

Each component's docs follow the Diataxis layout, so you can choose the kind of page that fits what you need right now.

A two-by-two grid of the four kinds of pages: tutorials, how-to guides,
explanation and reference, placed on a studying-to-working axis and a
theory-to-practice axis

Kind Read it when Router
Tutorial you are new to the component and want to see it work Route your first requests
How-to guide you have a specific task to get done router/how-to
Reference you need an exact name, default, key or signature router/reference
Explanation you want to know why it works the way it does router/explanation

Decisions that are hard to reverse are recorded separately as ADRs in docs/adrs/. These pages describe the code as it is on the branch they ship with, and they link to the source so you can check them. When the code and a page disagree, the code is right, and the page needs a fix in the same PR that changed the behavior.