Skip to main content

Tributary Getting Started

Outcome​

Use this page to confirm whether Tributary is the correct subsystem and which package boundary to inspect first.

What You Will Achieve​

By the end of this page, you should know whether your question belongs to reducers, snapshots, snapshot storage, or a neighboring layer above or below Tributary.

Before You Begin​

First Verified Success​

  1. Read the Tributary overview and confirm the problem is about reducers, snapshots, or derived state reconstruction.
  2. Open Tributary Reference and identify the package boundary that matches the work.
  3. If the issue is actually raw streams or domain behavior, switch to Brooks or Domain Modeling.

Choose Your Starting Point​

  • Start with Mississippi.Tributary.Abstractions for reducer and snapshot contracts.
  • Start with Mississippi.Tributary.Runtime for runtime reduction and snapshot behavior.
  • Start with Mississippi.Tributary.Runtime.Storage.Abstractions for snapshot storage seams.
  • Start with Mississippi.Tributary.Runtime.Storage.Cosmos for the Cosmos-backed snapshot storage implementation.

Verify You Are In The Right Section​

  • Stay in Tributary when the concern is derived state reconstruction or snapshots.
  • Move to Brooks when the concern is raw streams.
  • Move to Domain Modeling when the concern is domain behavior.

Verify The Result​

  • You should be able to explain whether the issue is reduction-layer work or a neighboring layer above or below it.

Current Scope​

This page covers package selection and subsystem orientation. For runnable reducer examples, see the Spring sample projections tutorial.

Summary​

Tributary is the correct entry point when the problem is the reduction and snapshot layer.

Next Steps​