Seperate Publish-Subscribe Module for DB Changes
The idea is to allow separate publish-subscribe mechanism then the DB framework used.
The controller would sync and read the DB, but receive update notifications and DB changes using the pub-sub mechanism.
This will allow implementing pub-sub even for DB's that dont support it and also be able to optimize this process
for scale and performance unrelated to the backend DB solution
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- Gal Sagie
- Direction:
- Approved
- Assignee:
- Eran Gampel
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Omer Anson
- Completed by
- Omer Anson
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add publish subscribe module installation
Addressed by: https:/
Add pub-sub abstraction to Dragonflow
Addressed by: https:/
Add publish-subscribe abstraction spec
Gerrit topic: https:/
Addressed by: https:/
Add support for DF built-in pub/sub
Gerrit topic: https:/
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Add support for DF built-in Pluggable pub/sub
Gerrit topic: https:/
Gerrit topic: https:/