feat(controller) batch controller should publish batch messages#84
Merged
Conversation
behinddwalls
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
feat(controller) batch controller should publish batch messages
What
The batch controller now constructs an entity. It publishes that batch (instead of the raw request) to the next pipeline stage. Supporting serialization methods (ToBytes/BatchFromBytes) were added to the Batch entity.
Why
The downstream stages of the pipeline need to operate on batches, not individual requests. This change shifts the publish boundary from request-oriented to batch-oriented, which is the batch controller's core responsibility — receiving requests and outputting batches.
Test Plan
Issues
#86