There are no strict restrictions in RabbitMQ brokers. The broker will use all available resources (if you do not set restrictions for some of them, they are called watermarks in the terminology of RabbitMQ).
There are some restrictions imposed by Erlang itself, such as the maximum number of simultaneous processes, but if you can theoretically achieve them on one node, then it is always useful to use distributed functions .
There is a lot of discussion about the needs and limitations of RabbitMQ resources,
PS However, there is a limit to the AMQP protocol. They are described in section 4.9 Limitations.
AMQP specifications impose these restrictions on future AMQP extensions or protocols from the same wire-level format:
- Number of channels per connection: 16-bit channel number.
- Number of protocol classes: 16-bit class identifier.
- Number of methods for each protocol class: 16-bit method identifier.
AMQP specifications impose these data restrictions:
- Maximum short string size: 255 octets.
- Maximum size of a long row or field table: 32-bit size.
- Maximum frame payload size: 32-bit size.
- Maximum content size: 64-bit.
The server or client can also impose its own resources restrictions, such as the number of simultaneous connections, the number of consumers per channel, the number of queues, etc. This does not affect interoperability and is not indicated.
pinepain Apr 10 2018-12-14T00: 00Z
source share