Pete Walsh

We probably don't need both the Delivery and Message data structures. There is a lot of duplication between the two.


Do we need to handle CPU bound tasks differently?

2

Is the tokio multi-threaded work-stealing runtime enough? One option is to handle CPU vs IO bound tasks differently by using [`spawn_blocking`](https://docs.rs/tokio/0.2.10/tokio/task/fn.spawn_blocking.html) or another thread pool instead of `spawn` for CPU...

There are a lot of configuration options missing from `BeatBuilder`. But all of these overlap with what's in `CeleryBuilder`.

- [ ] concurrency - [ ] `acks_late`

Document FAQs

6

- [ ] Should I run a CPU bound worker differently than an IO bound worker?

For example, - [ ] Tasks should never panic. Return an error with `?` instead. - [ ] Task timeouts only work when task is non-blocking. If your wrote a...

Include exchange info and routing keys when declaring queues

4

Like https://docs.celeryproject.org/en/latest/userguide/routing.html#how-the-queues-are-defined. Only relevant to AMQP. See https://docs.rs/lapin/0.28.4/lapin/struct.Channel.html#method.exchange_declare