Rabbitmq - Revision history

Pchero: /* Publish / Subscribe */

2021-03-08T04:06:32Z

Publish / Subscribe

← Older revision		Revision as of 04:06, 8 March 2021
Line 104:		Line 104:

	== Publish / Subscribe ==		== Publish / Subscribe ==
			The assumption behind a work queue is that each task is delivered to exactly one worker. The publish/subscribe allows deliver a message to multiple consumers.

	Essentially, publishing is going to be broadcast to all the receivers.		Essentially, publishing is going to be broadcast to all the receivers.

2020-05-16T05:47:39Z

RPC

← Older revision		Revision as of 05:47, 16 May 2020
Line 266:		Line 266:

	== RPC ==		== RPC ==

			== Scheduled message ==
			* https://www.rabbitmq.com/blog/2015/04/16/scheduling-messages-with-rabbitmq/

	== See also ==		== See also ==

2020-04-13T20:01:29Z

Fair dispatch

← Older revision		Revision as of 20:01, 13 April 2020
Line 97:		Line 97:
	==== Queue size ====		==== Queue size ====
	If all the workers are busy, your queue can fill up. You will want to keep an eye on that, and maybe add more workers, or use message TTL.		If all the workers are busy, your queue can fill up. You will want to keep an eye on that, and maybe add more workers, or use message TTL.

			=== Exclusive queues ===
			An exclusive queue can only be used (consumed from, purged, deleted, etc) by its declaring connection. An attempt to use an exclusive queue from a different connection will result in a channel-level exception(RESOURCE_LOCKEC) with an error message that says "cannot obtain exclusive access to locked queue".

			Exclusive queues are deleted when their declaring connection is closed or gone (e.g. due to underlying TCP connection loss). They therefore are only suitable for client-specific transient state.

	== Publish / Subscribe ==		== Publish / Subscribe ==

2020-04-09T20:32:05Z

Topic

← Older revision		Revision as of 20:32, 9 April 2020
Line 259:		Line 259:
	: *(star) can substitute for exactly one word.		: *(star) can substitute for exactly one word.
	: #(hash) can substitute for zero or more words.		: #(hash) can substitute for zero or more words.

			== RPC ==

	== See also ==		== See also ==

2020-02-21T14:20:43Z

2020-02-21T14:20:14Z

= Topic exchange

← Older revision		Revision as of 14:20, 21 February 2020
Line 253:		Line 253:
	== Topic ==		== Topic ==

	=== Topic exchange ==		=== Topic exchange ===
	Messages sent to a topic exchange can't have an arbitrary 'routing_key' - it must be a list of words, delimited by dots. The words can be anything, but usually they specify some features connected to the message. A few valid routing key examples: *stock.usd.nyse, nyse.vmw, quick.orange.rabbit. There can be as many words in the routing key as you like, up to the limit of 255 bytes.		Messages sent to a topic exchange can't have an arbitrary 'routing_key' - it must be a list of words, delimited by dots. The words can be anything, but usually they specify some features connected to the message. A few valid routing key examples: *stock.usd.nyse, nyse.vmw, quick.orange.rabbit. There can be as many words in the routing key as you like, up to the limit of 255 bytes.

2018-12-09T14:21:34Z

Subscripting

← Older revision		Revision as of 14:21, 9 December 2018
Line 250:		Line 250:
	}		}
	</source>		</source>

			== Topic ==

			=== Topic exchange ==
			Messages sent to a topic exchange can't have an arbitrary 'routing_key' - it must be a list of words, delimited by dots. The words can be anything, but usually they specify some features connected to the message. A few valid routing key examples: *stock.usd.nyse, nyse.vmw, quick.orange.rabbit. There can be as many words in the routing key as you like, up to the limit of 255 bytes.

			The binding key must also be in the same form. The logic behind the 'topic' exchange is similar to a 'direct' one - a message sent with a particular routing key will be delivered to all the queues that are bound with a matching binding key. However there are two important special cases for binding keys:
			: *(star) can substitute for exactly one word.
			: #(hash) can substitute for zero or more words.

	== See also ==		== See also ==

2018-12-08T23:26:22Z

Bindings

@@ Line 168: / Line 168: @@
 </source>
 The meaning of a binding key depends on the exchange type. The 'fanout' exchanges, which we used previously, simply ignored its value.
 == See also ==

2018-12-08T23:08:19Z

2018-12-08T20:39:00Z

← Older revision		Revision as of 20:39, 8 December 2018
Line 139:		Line 139:
	When the connection that declared it closes, the queue will be deleted because it is declared as exclusive.		When the connection that declared it closes, the queue will be deleted because it is declared as exclusive.

	===		=== Bindings ===
			We've already created a fanout exchange and a queue. Now we need to tell the exchange to send messages to our queue. That relationship between exchange and a queue is called a binding.
			<source lang=go>
			err = ch.QueueBind(
			q.Name, // queue name
			"", // routing key
			"logs", // exchange
			false,
			nil
			)
			</source>
			From now on the logs exchange will append message to our queue.

	== See also ==		== See also ==

← Older revision		Revision as of 14:20, 21 February 2020
Line 262:		Line 262:
	== See also ==		== See also ==
	* https://www.rabbitmq.com/		* https://www.rabbitmq.com/
			* https://www.katacoda.com/javajon/courses/kubernetes-applications/rabbitmq - deploy rabbitmq on the kubernetes

	[[category:system]]		[[category:system]]