Skip to content

Rough sketch of listening to Kafka for update notifications#199

Draft
takluyver wants to merge 1 commit into
mainfrom
feat/kafka-updates
Draft

Rough sketch of listening to Kafka for update notifications#199
takluyver wants to merge 1 commit into
mainfrom
feat/kafka-updates

Conversation

@takluyver
Copy link
Copy Markdown
Member

@CammilleCC this probably won't work as is, I haven't tried to test it at all, but it's meant to be a starting point for using Kafka notifications rather than polling.

The idea is that when the first client subscribes to a proposal, it creates and starts a DBWatcher object. Extra subscribers then get added to that, so they only hit the database once. When a subscription is closed, the generator task should be cancelled, and the last subscriber should also cancel the DBWatcher.

@takluyver takluyver force-pushed the feat/kafka-updates branch from 6c50ee2 to 4df9b74 Compare May 6, 2026 14:13
@takluyver takluyver force-pushed the feat/kafka-updates branch from 4df9b74 to 15f502a Compare May 6, 2026 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant