Epic: Phase 3 — ES Primary Read/Write #165
Labels
No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#13 Production-Ready Event Sourcing
aethyr/Aethyr
#166 Implement ProjectionReadModel query layer
aethyr/Aethyr
Reference: aethyr/Aethyr#165
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Background and Context
In Phase 3, game reads are served from ES projection read models instead of GDBM. GDBM becomes a best-effort secondary that is written to for backward compatibility but never read from during normal operation. This requires a
ProjectionReadModelquery layer and switchingGary/CacheGaryto read from projections.Demonstrable Outcome
The game operates with reads from ES projections. GDBM is written but not read. Full world state verified consistent.
Acceptance Criteria
ProjectionReadModelquery layer serves object lookupsGary/CacheGaryread from projections in:primarymode:primarywrite mode implemented (ES first, GDBM best-effort)