"Section 9 Rabbitmq" in "Chapter Three [Supplementary Information] Detailed Explanation of Common Message Middleware Application" in "Special Topic Four Service Transformation"

"3.9.1 RabbitMQ entry and message distribution mechanism"

  • 2 5 RabbitMQ configuration:
    Insert picture description here
  • 42 points RabbitMQ architecture:
    Insert picture description here
    If the message does not specify an exchange, it can be posted to the default exchange and delivered by queue name.
    The routeKey of the message must exactly match the bindingKey of the direct type of exchange, and the bindingKey of the topic type of exchange can be fuzzy matching.
    Routing key in fanout mode is meaningless, it will route all messages sent to this exchange to the queue bound to this exchange.
    The header type exchange also does not need a routing key, but is routed by attributes

85:49:
Insert picture description here

  • 70 minutes temporary queue
  • 77 points channel.basicQos

"3.9.2 Cluster and High Availability"

  • 29 30 cluster normal mode:
    Insert picture description here

  • 11 50+ Mirror queue mode: not only synchronizes metadata, but also synchronizes data, which can avoid single points of failure.
    31 35+: (It is not necessary to send data to all nodes. You can customize the rules, such as sending to a specified number of Node)
    Insert picture description here

"3.9.3 Persistence and Memory Disk Management"

Insert picture description here

  • 8 50 RabbitMQ memory alarm:
    Insert picture description here
  • 12 points RabbitMQ memory paging:
    Insert picture description here
  • 14 points RabbitMQ disk alarm
    Insert picture description here

"3.9.4 Message Reliability and Plug-in Mechanism"

Guess you like

Origin blog.csdn.net/qq_23204557/article/details/112131146