Event Persistence Infrastructure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Description
Create database infrastructure for persisting event timestamps to enable reconciliation after disconnection. eg: with this, Gateway can request control-plane to return updates after a certain timestamp (last updated at gateway side) so that gateway can reconciliate them.
(This task is to track DB level changes of it)
What will be accomplished
- Define event timestamp data model and database schema
- Implement repository layer for timestamp persistence operations
- Add database initialization and migration logic
- Integrate event repository with control plane client
Related User Story
Persistent Connection Maintenance - Gateway maintains persistent WebSocket connection for real-time event delivery
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the event timestamp data model, database schema, repository layer, migration or initialization logic, and control-plane client mentioned in the issue. Define completion around persistent timestamp operations, database setup and migration support, and repository integration with the control-plane client for reconciliation after disconnection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100