Skip to main content

Troubleshoot Aqueduct Scope And Entry-Point Confusion

Use this guide when you started in Aqueduct, but the question now seems to involve projections, domain behavior, or client concerns.

Symptoms​

  • You started in Aqueduct, but the question now seems to involve projections, domain behavior, or client concerns.

What This Usually Means​

Aqueduct is the wrong entry point when the real question is above the backplane layer.

Probable Causes​

  • The task is actually about Inlet and full-stack projection delivery.
  • The task is actually about Domain Modeling and domain behavior.
  • The task is actually about client state or UI composition, which belongs in Reservoir or Refraction.

How To Confirm​

  • Stay in Aqueduct only if the concern is Orleans-backed SignalR backplane infrastructure.
  • Move sections if the concern is generated surfaces, domain behavior, or client composition.

Resolution​

Use How To Choose An Aqueduct Package Entry Point if the problem still belongs to Aqueduct. Otherwise switch to the correct subsystem overview and continue there.

Verify The Fix​

You should be able to describe the problem in one sentence using either backplane infrastructure, generated composition, domain behavior, or client state and UI as the primary concern.

Prevention​

Start each investigation from the subsystem boundary first, not from a package name alone.

Summary​

Aqueduct is only the right section when the problem is the distributed real-time backplane itself.

Next Steps​