Inlet Concepts
Problem This Area Solves
Inlet exists to keep client, gateway, and runtime surfaces aligned so teams do not have to rebuild the same transport and projection surface by hand.
Core Idea
Source generators and runtime packages work together so projection DTOs, APIs, registrations, and subscription wiring stay synchronized.
How It Fits The Stack
Inlet is the composition layer that ties together Aqueduct, Reservoir, and Domain Modeling.
What This Area Owns
- Shared abstractions for projection paths and related metadata
- Client support for projection state and subscriptions
- Gateway support for generated APIs and SignalR delivery
- Runtime support for discovery and generated registrations
- Source generators that align those layers
What This Area Does Not Own
- The underlying real-time backplane by itself
- The domain behavior layer by itself
- The client-state model by itself
What This Page Guarantees
- It defines Inlet as the cross-layer composition boundary that aligns client, gateway, and runtime surfaces.
- It identifies the single-subsystem areas readers should switch to when the problem does not actually span multiple layers.
What This Page Does Not Claim
- Full generated output reference or generator contract reference
- Runtime registration guarantees, deployment guarantees, or operational defaults
- Complete end-to-end walkthrough material beyond the verified sample links provided here
Trade-Off To Keep In Mind
Inlet reduces duplicated cross-layer plumbing, but it only makes sense when the problem truly spans multiple layers rather than one subsystem in isolation.
Summary
Think of Inlet as the layer that keeps Mississippi surfaces aligned across the stack.