What is eventually consistent is the job state: it means that jobs are removed only when they are successfully delivered at least one time. Best effort orderin

What is eventually consistent is the job state: it means that jobs are removed only when they are successfully delivered at least one time. Best effort ordering does not mean no ordering btw. Use cases for which strict ordering is needed are rare, and it is possible to build order out of an unordered queue if strictly needed (especially since, when strict ordering is needed, usually you have a source of truth to maintain the state of the application, that happens to be a strictly consistent store). The cost of ordering is huge in terms of design, and benefits just an handful of use cases. So I think best effort ordering is one of the best Disque assets.