Skip to content

docs: report what Gumbo needs for durable execution frameworks #19

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
contrasam merged 3 commits into from
Jul 26, 2026
Merged

docs: report what Gumbo needs for durable execution frameworks #19

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4799da4
docs: report what Gumbo needs for durable execution frameworks
claude Jul 26, 2026
b0f456c
docs: resolve the localId vs streamVersion question in the Gumbo report
claude Jul 26, 2026
1e92d97
docs: correct the sequence-density claim in the Gumbo report
claude Jul 26, 2026
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
4 changes: 4 additions & 0 deletions docs/distribution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,6 +115,10 @@ thing: losing the node loses the state, so you need membership, a global registr
Catalyst's state is not in the process — it is in the log, and `resume(id)` can reconstitute it
anywhere. Solving the weaker problem is what lets the operational story be this small.

> The full set of Gumbo defects and missing primitives this design depends on — with the evidence for
> each, a suggested order, and the tests that would have caught them — is written up separately in
> [`gumbo-requirements.md`](gumbo-requirements.md).

## Prerequisite: Gumbo is not multi-writer safe today

This was measured, not assumed. Two JVMs were pointed at one Gumbo directory and each appended three
Expand Down
Loading
Loading