Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore events base queues as a strategy #19

Open
thoven87 opened this issue Feb 22, 2025 · 3 comments
Open

Explore events base queues as a strategy #19

thoven87 opened this issue Feb 22, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@thoven87
Copy link
Contributor

Currently, we poll by default every 100ms for jobs unless a user change this on the config.

I think it'll be beneficial to also support Postgres LISTEN / NOTIFY (yes, the payload limit is 8KB) it would help with #17
I see PostgresNIO has support for LISTEN / NOTIFY, but it's not well documented. Maybe @fabianfett can help point us in the right direction?

What do you think @adam-fowler @Joannis ?

@thoven87 thoven87 added the enhancement New feature or request label Feb 22, 2025
@adam-fowler
Copy link
Member

It is worth looking into for sure. We should setup a proper benchmark to verify performance changes.

@adam-fowler
Copy link
Member

What happens if the a job is added to the queue, but no job handler is running ie the LISTEN/NOTIFY is not running

@thoven87
Copy link
Contributor Author

What happens if the a job is added to the queue, but no job handler is running ie the LISTEN/NOTIFY is not running

These jobs won't be processed and marked as failed. The queue.cleanup func can be used to rerun these jobs should a job handler which can process these jobs become available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants