confirm vs transactional channel

[moshe cohen]

what is the difference between these two channel states ?

which preform better ?

thanks,

Moshe

[Wesley Peng]

on 2019/9/12 16:17, moshe cohen wrote:
> what is the difference between these two channel states ?
>

1. confirm is set for one message, while transaction can have
multi-messages included.

2. confirm is for producer only, but transaction can be used for both
producer and consumer.

3. both are going with low efficiency.

regards.

[Karl Nilsson]

It is not correct that both options give low efficiency. The low performance argument is true for transactional channels but not for publisher confirms where the overhead is minimal if you use your client library correctly. In fact I am running performance tests atm and see almost no difference between using publisher confirms and not.

For good throughout you must not block waiting for confirms - most clients provide an asynchronous notification option when the confirm notifications come in that should be used instead.

Cheers

Karl

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/7a7dd719-dc3b-75eb-06bc-82f8d723f3c7%40thepeng.eu.

--

Karl Nilsson

[Wesley Peng]

Hi

on 2019/9/12 16:37, Karl Nilsson wrote:
> For good throughout you must not block waiting for confirms - most
> clients provide an asynchronous notification option when the confirm
> notifications come in that should be used instead.

Yes you are right. if using a asynchronous library the publish confirm
should not become low effective.

thanks.