Show HN: Broccoli – message queue for Rust applications, alternative to Celery github.com 30 points by skeptrune 7 days ago
klaussilveira 7 days ago Interesting. Developer experience seems nice. Any plans of adding the concept of unique jobs or scheduled jobs? denssumesh 7 days 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 7 days ago Examples: https://github.com/noxdafox/rabbitmq-message-deduplicationhttps://nats.io/blog/new-per-subject-discard-policy/ denssumesh 5 days ago So ensuring that each message has a unique payload?
denssumesh 7 days 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 7 days ago Examples: https://github.com/noxdafox/rabbitmq-message-deduplicationhttps://nats.io/blog/new-per-subject-discard-policy/ denssumesh 5 days ago So ensuring that each message has a unique payload?
klaussilveira 7 days ago Examples: https://github.com/noxdafox/rabbitmq-message-deduplicationhttps://nats.io/blog/new-per-subject-discard-policy/ denssumesh 5 days 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?