Repository navigation
Conversation
commit: |
reeceyang
force-pushed
the
reece/aggregate-migration-docs
branch
from
November 14, 2026 05:49
f96b8b0 to
89970e9
Compare
reeceyang
changed the base branch from
reece/namespace-prefix
to
reece/safe-clear-all
November 14, 2026 05:49
reeceyang
force-pushed
the
reece/safe-clear-all
branch
from
November 16, 2026 20:51
1a18de6 to
0bad93c
Compare
reeceyang
force-pushed
the
reece/aggregate-migration-docs
branch
from
November 16, 2026 20:51
89970e9 to
a736a06
Compare
Contributor
Author
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.
Adds a README section on moving an aggregate's data into a new aggregate while the app keeps running: dual-write with the idempotent methods, backfill from the table or copy from the old aggregate, verify, switch reads, then clean up. Also covers the pitfalls found while testing this end to end on a local deployment: verifying against the table rather than the old aggregate, keeping a new aggregate out of an unprefixed aggregate's component, and deleting the old component from the dashboard, since unmounting it keeps its data.
Stack
🤖 Generated with Claude Code