Skip to main content

API & Client Sync (Inlet)

Overview​

Inlet is the Mississippi composition layer.

It uses source generators plus client, gateway, and runtime packages to keep projection DTOs, generated HTTP endpoints, runtime registrations, and client subscription wiring aligned across the full stack.

Why This Area Exists​

Use Inlet when the problem is alignment across client, HTTP, and runtime surfaces rather than any one layer in isolation.

It exists to keep generated contracts and runtime wiring synchronized so teams can model the domain once and avoid rebuilding the same transport and projection surface repeatedly.

Representative Packages​

  • Mississippi.Inlet.Abstractions
  • Mississippi.Inlet.Client
  • Mississippi.Inlet.Gateway
  • Mississippi.Inlet.Runtime

What This Area Owns​

  • Shared abstractions for projection paths and related metadata
  • Client runtime support for projection state and subscriptions
  • Gateway runtime support for generated APIs and SignalR delivery
  • Runtime registration support for projection discovery and generated silo wiring
  • Source generators that produce aligned code across those layers

How It Fits Mississippi​

Inlet is the layer that ties the rest of the stack together.

It composes with Aqueduct for real-time delivery, with Reservoir on the client, and with Domain Modeling and Tributary for projection and domain registration surfaces.

Use This Section​

Start here when you need to understand generated projection, API, and registration alignment across the full Mississippi stack.

Build With Inlet​

Use Generated Application Contracts to connect domain inputs to each host's registrations. Then keep a workspace projection live across Blazor page navigation.

The generated contracts let teams concentrate their review on business rules and typed boundaries. Those same boundaries give AI-assisted implementation a repeatable path from domain changes to consumer verification.

Learn More​