Merge alt event store into core with JSON serialization and Prometheus metrics #36
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
Reference: aethyr/Aethyr#36
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?
Metadata
refactor(event-sourcing): consolidate ImmuDB event store with JSON serialization and Prometheus metricsfeature/m1-v12-consolidate-event-storeBackground
Two ImmuDB event store implementations exist. The core version uses Marshal (insecure binary serialization) with no metrics. The alt version at
lib/aethyr/event_sourcing/immudb_event_store.rbuses JSON/Oj with Prometheus counters and optimistic locking but is never wired in.Expected Behavior
A single canonical event store at
lib/aethyr/core/event_sourcing/immudb_event_store.rbthat combines the best of both: JSON serialization via Oj, Prometheus metrics, optimistic concurrency, file-based fallback, and configuration viaServerConfig.Acceptance Criteria
events_committed_total,event_commit_latency_seconds,snapshot_operations_totalServerConfig(no separateConfigurationsingleton)Subtasks
evt/{id}/{seq}andsnap/{id}/{seq}sequent_setup.rbto use the consolidated storebundle exec rake unit, fix any errorsDefinition of Done
This issue is complete when:
master, reviewed, and merged.