My main problem with Celery is their cowboy handling of distributed computing combined with poor documentation. I'm not aware of any documentation making it cle

My main problem with Celery is their cowboy handling of distributed computing combined with poor documentation. I'm not aware of any documentation making it clear what's their choices for not-exactly-once result, for one. Failure modes aren't obvious either. Do we need to make sure that tasks are idempotent? Is there any chance they'll be retried if a worker dies suddenly? What exactly happens when a worker receives SIGKILL? How all of the above works with their Fabric (task orchestration) stuff? I just can't trust a product that doesn't even discuss those issues prominently in the documentation. Distributed computing is inherent for a background task queue, and it's one of the hardest problems out there, so their best effort patchwork of retries and checks doesn't cut it for me. They seem to code and document for a happy case, which is a huge red flag.