The mental model behind every feature page: how Arion is put together, how a request travels through it, and how configuration reaches it.
Concepts
How Arion works: the architecture, the life of a request, the filter chain, the configuration model and the Envoy compatibility promise.
6 pages
In this group
- ArchitectureHow the Arion process is organized: a services runtime for control work, proxy runtimes for the data path, and channels between them. Read →
- Life of a requestThe path a connection and its requests take through Arion, from accept to upstream and back, and where each filter runs. Read →
- The filter chainThe three levels filters attach at, the ordering rules Arion enforces, and how routes override or disable individual HTTP filters. Read →
- The configuration modelThe Arion file's top-level keys, how flags and environment variables override them, and how static and dynamic resources fit together. Read →
- Runtime and threadingOne multi-threaded runtime or one runtime per core: the runtime block, CPU detection, core pinning, and what SO_REUSEPORT changes. Read →
- Envoy compatibilityThe promise Arion makes about Envoy configs: accepted means Envoy-like behavior; anything it cannot honor is refused, never ignored. Read →