Show HN: Broccoli – message queue for Rust applications, alternative to Celery github.com 31 points by skeptrune 10 months ago
klaussilveira 10 months ago Interesting. Developer experience seems nice. Any plans of adding the concept of unique jobs or scheduled jobs? denssumesh 10 months ago I'm not sure what you mean by unique jobs, but for scheduled jobs, it could definitely be on the roadmap. I'm still deciding whether or not its a good idea to make it more of an actual service than just a library. klaussilveira 10 months ago Examples: https://github.com/noxdafox/rabbitmq-message-deduplicationhttps://nats.io/blog/new-per-subject-discard-policy/ denssumesh 10 months ago So ensuring that each message has a unique payload?
denssumesh 10 months ago I'm not sure what you mean by unique jobs, but for scheduled jobs, it could definitely be on the roadmap. I'm still deciding whether or not its a good idea to make it more of an actual service than just a library. klaussilveira 10 months ago Examples: https://github.com/noxdafox/rabbitmq-message-deduplicationhttps://nats.io/blog/new-per-subject-discard-policy/ denssumesh 10 months ago So ensuring that each message has a unique payload?
klaussilveira 10 months ago Examples: https://github.com/noxdafox/rabbitmq-message-deduplicationhttps://nats.io/blog/new-per-subject-discard-policy/ denssumesh 10 months ago So ensuring that each message has a unique payload?
Interesting. Developer experience seems nice. Any plans of adding the concept of unique jobs or scheduled jobs?
I'm not sure what you mean by unique jobs, but for scheduled jobs, it could definitely be on the roadmap. I'm still deciding whether or not its a good idea to make it more of an actual service than just a library.
Examples: https://github.com/noxdafox/rabbitmq-message-deduplication
https://nats.io/blog/new-per-subject-discard-policy/
So ensuring that each message has a unique payload?