tag:blogger.com,1999:blog-15136575.post5555004231201844042..comments2023-10-17T12:00:16.772+01:00Comments on Code rant: RabbitMQ Subscriptions with the DotNet ClientMike Hadlowhttp://www.blogger.com/profile/16441901713967254504noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-15136575.post-49778838573314627872012-05-07T14:33:59.267+01:002012-05-07T14:33:59.267+01:00Use Spring AMPQ. As for the actual settings, I am ...Use Spring AMPQ. As for the actual settings, I am not sure. We value reliability over speed (cause that is why one uses a queue) so we dumped RabbitMQ and went back to JMS (using ActiveMQ for .NET clients).<br /><br />http://www.springsource.org/spring-amqpAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-15136575.post-92152558189540298412011-07-11T12:44:49.557+01:002011-07-11T12:44:49.557+01:00Even in systems which I've had a high number o...Even in systems which I've had a high number of messages passing though, it's often better to scale out with RabbitMQ federation instead of ignoring the ACKs with consumption.Travis Smithhttp://legomaster.net/noreply@blogger.comtag:blogger.com,1999:blog-15136575.post-88412712799555380862011-07-11T12:18:47.323+01:002011-07-11T12:18:47.323+01:00That's great. I think we are going to use Rabb...That's great. I think we are going to use RabbitMQ and I realized how many settings you need to be aware of when developing something using the default client.<br /><br />The default settings you've chosen are sensible and conform to our scenario. We want reliability more than throughput.ovidurihttps://www.blogger.com/profile/14941065458815785242noreply@blogger.com