@korny: I was designing and implementing these 'message based services' in early 00's and I agree. I think mainly cos it forces thought about reconciling transactional data changes and using adjustment events to back out a change if you get a partial failure. It also moves the responsibility for ack/nack to the messaging infrastructure

Yeah - and it forces you to do your UX with async in mind. You end up doing that anyway - "your order is submitted" is never synchronous

morning