I meant this in the sense that, for most cases, a typical deploy of something (most likely RabbitMQ) is going to meet their needs. There's a large community, st

I meant this in the sense that, for most cases, a typical deploy of something (most likely RabbitMQ) is going to meet their needs. There's a large community, stable libraries for every library and plenty of blog posts and tutorials. Maybe you're doing something I consider atypical..maybe you're pushing more messages, have lower latency requirements, than I'm used to. But at that point, nothing "cloud" is going to help (at least, certainly not something like SQS). For what it's worth, we essentially treat a write to our queue as fundamentally important as a write to our DB (wrapping the latter in a transaction of the former). This helps make sure that reliability issues shouldn't go unnoticed (I've personally never seen RabbitMQ swallowing messages, though it is something I've heard about, but seemingly always from relatively outdated versions).