Saurabh Nanda

@kanagarajkm It would be great if you could share how you're using `odd-jobs`. I've listed down some questions at https://github.com/saurabhnanda/odd-jobs/issues/44#issuecomment-694649163 , but would be happy to head any feedabck.

Thanks for offering to help @SanchayanMaity Broadly I'm expecting there would be a few points of integration: - Integrating the web UI - Writing wrappers on top of `createJob` and...

@SanchayanMaity were you able to spend any time on this?

Cool - let's wait. Hopefully you can get started by next week :-) On Sat, Oct 31, 2020 at 6:03 PM Sanchayan Maity wrote: > @saurabhnanda I had started looking...

Anyone with reservations about this PR? Else I'll merge it in a few days. @ivb-supercede @kanagarajkm @tfausak @tchoutri

If my calculation is right, even at one job / sec, it would take 17+ years to reach this limit. Are you planning to use this instead of a message...

Seriously? Are you planning to use odd-jobs instead of a message-queue? How many messages / sec are you expecting?

> Is Int being used to address a particular problem with performance or overhead, or just because it's not an expected use-case for the queue to grow beyond 2^29 entries?...

So, _ideally_, if we make this change it should be `int Int` and `bigint Int64`, right? Is there value in making this configurable? Or will it end-up being unnecessary complexity...

Did you get a chance to review this PR?