Skip to main content

Aqueduct Getting Started

Overview​

Use this page to identify whether Aqueduct is the right subsystem for your problem and which package boundary to inspect first.

What You Will Achieve​

By the end of this page, you should know whether your question is about the Aqueduct backplane itself, a higher-level Inlet scenario, or a different Mississippi layer entirely.

Before You Begin​

  • Read the Aqueduct overview.
  • If your question is about projection delivery rather than backplane infrastructure, also read Inlet.

First Verified Success​

  1. Read the Aqueduct overview and confirm the problem is about Orleans-backed push delivery into SignalR rather than domain behavior or client state.
  2. Open Aqueduct Reference and identify which of the three package boundaries matches the question you are trying to answer.
  3. If the question is actually about full-stack projection delivery, switch immediately to Inlet instead of continuing here.

Choose Your Starting Point​

  • Start with Mississippi.Aqueduct.Abstractions when you need contracts and options without runtime hosting concerns.
  • Start with Mississippi.Aqueduct.Gateway when your question is about gateway-side hub lifetime management or notifier registration.
  • Start with Mississippi.Aqueduct.Runtime when your question is about runtime-side backplane registration.

Verify You Are In The Right Section​

  • Stay in Aqueduct when the concern is SignalR backplane behavior across hosts.
  • Move to Inlet when the concern is full-stack projection delivery.
  • Move to Domain Modeling when the concern is domain behavior rather than transport.

Verify The Result​

  • You should be able to name the correct package boundary or decide that the question belongs in Inlet instead.

Current Scope​

This page covers package selection and subsystem orientation. For runnable end-to-end examples, see the Spring sample.

Summary​

Aqueduct is the right starting point when the problem is Orleans-backed SignalR backplane infrastructure, not domain behavior or higher-level generated delivery surfaces.

Next Steps​