Clustering பல RabbitMQ nodes-களை ஒரு தர்க்க broker-ஆக இணைக்கிறது — scalability மற்றும் (replicated queues உடன்) high availability-க்கு. Clustering-ம் அதன் nuances-களைப் புரிந்துகொள்வது RabbitMQ-வை scalable-ஆகவும் reliable-ஆகவும் operate செய்வதற்கு முக்கியமாகும்.
Cluster என்பது என்ன
A RabbitMQ CLUSTER = multiple nodes acting as ONE logical broker:
→ nodes share METADATA (queue/exchange definitions, bindings, users, vhosts) across the cluster
→ clients can connect to any node; load is distributed across nodes
→ scales connection/channel capacity and distributes load
Cluster-ல் Queues (ஒரு முக்கியமான nuance)
⚠️ By default, a queue's DATA lives on ONE node (the node where it was declared):
→ other nodes know about the queue (metadata) but route to the owning node
→ if that node FAILS → the queue (and its messages) is UNAVAILABLE
→ so CLUSTERING ALONE does NOT make queues highly available!
→ for HA → use REPLICATED queues (QUORUM QUEUES) that replicate data across nodes
