<div dir="ltr">The database consulted by the exchange lives in the same memory space as RabbitMQ, it's an embedded database, so there is no network overhead.</div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Jun 3, 2013 at 1:39 PM, Tamir Agamy <span dir="ltr"><<a href="mailto:tamiragamy@gmail.com" target="_blank">tamiragamy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div><div>Hello<br><br></div>Earlier today I asked this question:<br>When binding a queue, what really happens? is the binding information being forward via the<br>server to the exchange, where it is entered to a binding list? or is the information saved at the<br>
server and the exchange has to inquire the server whenever it gets a message from the producer?<br><br></div>and was answered (by Emile Joubert):<br>"Exchanges don't really exist as independent entities in the broker. The<br>
bindings are stored in an internal database. This database is queried<br>
each time a message is received."<br><br><br>So, f I understand correctly, then everytime the publisher
sends a message to the exchange, the exchange has to inquire the
database in order to see which queues (if any) are waiting to recieve
the message.<br>
If that is the case, then we're not really saving network
transportation, each message that the publisher produces will result in
contacting the server, even if there are no subscribers to this
publisher.<br>
Is that so?<br><br></div>With regards,<br>Tamir<br></div>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br></div>