Clear boundaries. A coherent system.
Explore the stack by responsibility. Select a layer to understand its role.
Application layer
Organize Actions, routes, request results, notifications, and streams. Separate configuration and serialization modules connect business code to infrastructure.
Read the module guide →Coordination layer
Discover service instances and select targets through routing rules and strategies. Caches and placement coordinate entity bindings; monitor evaluates pressure for new selections.
Read the module guide →Connectivity layer
Organize connections and messages for clients, servers, and gateways. NX frame codecs and QUIC, TCP, and WebSocket transports live in distinct modules.
Read the module guide →Observability
Telemetry implementations depend on observation interfaces in components. OpenTelemetry provides tracing and metrics. Starter and Agent are mutually exclusive integration modes.
Read the module guide →What responsibilities shape an interaction?
A reading map for the source. Actual deployment topology and request paths depend on application configuration.
Make lifecycle decisions explicit.
Discovery, node selection, resource initialization, and ownership are separate responsibilities. Placement does not create resources or renew automatically; zero monitor weight does not migrate existing entities.
Read the placement contract →Discovery → Instance snapshot
Routing → Target selection
Placement → Entity binding
Application → Resource lifecycle
Telemetry → Observation