Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

66.
The Problem
•
Queues contents live in the node where the Queue was declared

67.
The Problem
•
Queues contents live in the node where the Queue was declared
•
A cluster can access the queue from every connected node

68.
The Problem
•
Queues contents live in the node where the Queue was declared
•
A cluster can access the queue from every connected node
•
Queues are an Erlang process (tied to one core)

69.
The Problem
•
Queues contents live in the node where the Queue was declared
•
A cluster can access the queue from every connected node
•
Queues are an Erlang process (tied to one core)
•
Adding more nodes doesn’t really help

84.
With RabbitMQ we can
•
Ingest data using various protocols: AMQP, MQTT and STOMP

85.
With RabbitMQ we can
•
Ingest data using various protocols: AMQP, MQTT and STOMP
•
Distribute that data globally using Federation

86.
With RabbitMQ we can
•
Ingest data using various protocols: AMQP, MQTT and STOMP
•
Distribute that data globally using Federation
•
Scale up using Sharding

87.
With RabbitMQ we can
•
Ingest data using various protocols: AMQP, MQTT and STOMP
•
Distribute that data globally using Federation
•
Scale up using Sharding
•
Load balance consumers with Federated Queues