yes - I know what you mean. Part of the reason is that there has been an entire body of effort into making queues scale and be available. Interestingly, just t

yes - I know what you mean. Part of the reason is that there has been an entire body of effort into making queues scale and be available. Interestingly, just today I discovered a new queue that I did not know of before, written in Go [1] that keeps everything in memory and tries to fail over. I think by the time you need a distributed commit, you have the staffing required to build a queue that scales and does not go down. So there is less focus on semantics of distributed commit (which needs a lot of complexity on the application side and is hard to reason about), than to build a scalable queue. [1] https://github.com/bitly/nsq https://github.com/bitly/nsq