Skip to content

Add service protocol V7 with streaming eager state support#4413

Open
tillrohrmann wants to merge 1 commit intorestatedev:mainfrom
tillrohrmann:issues/4344
Open

Add service protocol V7 with streaming eager state support#4413
tillrohrmann wants to merge 1 commit intorestatedev:mainfrom
tillrohrmann:issues/4344

Conversation

@tillrohrmann
Copy link
Copy Markdown
Contributor

Extend the service protocol with V7 that streams state entries in batches after the StartMessage, allowing eager state to exceed the max message size limit (~32MB). Two new Control messages are added:

  • EagerStateEntryMessage (0x0006): carries batches of state KV pairs
  • EagerStateCompleteMessage (0x0007): terminates the state stream

State is streamed in ~1MB batches to stay well under the message size limit. V1-V6 behavior is completely unchanged.

Closes #4344

Extend the service protocol with V7 that streams state entries in
batches after the StartMessage, allowing eager state to exceed the
max message size limit (~32MB). Two new Control messages are added:

- EagerStateEntryMessage (0x0006): carries batches of state KV pairs
- EagerStateCompleteMessage (0x0007): terminates the state stream

State is streamed in ~1MB batches to stay well under the message size
limit. V1-V6 behavior is completely unchanged.

Closes restatedev#4344
@tillrohrmann tillrohrmann marked this pull request as ready for review March 31, 2026 13:40
Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stream state entries to service endpoints instead of materializing all in StartMessage

1 participant