Skip to content

Docs: no links to the private CritterWatch repo #5775

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeremydmiller merged 1 commit into from
Oct 27, 2026
+1 −2
Merged

Docs: no links to the private CritterWatch repo #5775

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/events/multitenancy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,8 +132,7 @@ be appended as the default tenant id _no matter what the session's tenant id is_
This is an advanced, opt-in option aimed at large multi-tenanted event stores where a single, shared
event store becomes a scalability bottleneck. It builds on the conjoined event tenancy described above
by physically isolating each tenant's events and giving the async daemon a per-tenant view of progress.
See [JasperFx/marten#4596](https://github.com/JasperFx/marten/issues/4596) and
[CritterStack #209](https://github.com/JasperFx/CritterWatch/issues/209) for the full design.
See [JasperFx/marten#4596](https://github.com/JasperFx/marten/issues/4596) for the full design.
:::

For systems with many tenants and very high event volumes, you can opt into **per-tenant event partitioning**.
Expand Down
Loading