Architecture and design

Mongoose hosts event processors on Agrona agent threads. Each processor group also runs a generated Fluxtion control processor that decides its lifecycle changes. These pages describe the unreleased control-plane candidate; see the release notes for caller-visible changes.

Start here	What it explains
Architecture overview	The runtime, its thread boundaries and the two event paths
Components and ownership	Who owns registrations, queues, services and capture resources
Mongoose built with Fluxtion	Why the runtime uses its own event-processing technology
Event flow	Publication, subscriptions, delivery, retries and overload
Sequence diagrams	Subscription, event delivery, control, capture and shutdown
Agent execution	Choosing and hosting cooperative workers
Threading model	Callback contexts, waiting rules, core pinning and idle strategies
Object pooling	Reference ownership across fan-out and release
Server control	Admin commands and the programmatic controller
Deployment	JVM requirements, shutdown and recovery limits
Case study: a late capture completion	Following real qualification evidence through the analyser

The diagrams are editable SVGs, scale without losing detail and follow the site's light/dark theme. Solid arrows show the flow labelled on each diagram; they do not imply that the entire server has one global event order. The control-plane contracts give the exact API guarantees and failure outcomes.