Broker of messages (broker)
Description
System message broker.
Receives and stores data without violating arrival order.
Guarantees delivery of received messages to consumers. When a consumer takes a message, the message is automatically deleted (unlike well-known brokers that retain messages for some time). +
Temporarily and limitedly stores event data in various processes generated on the current site.
Used as a task queue for post-processing processes (CDR aggregator, mixer, packager, transcriber, etc.).
Made redundant in Active-Passive mode.
Scaled by splitting into groups by domains. Potentially, if performance is insufficient, it can be split into groups by queue names. Fundamental rule: one queue - one group.
Code |
|
Operation mode |
|
Redundancy mode |
|
Site types |
|
Layer |
|
Placement |
|
State preservation and recovery on restart |
|
Application |
|
Own storage |
|
Limitations
-
Maximum number of elements in one queue is 2 million. After reaching the limit, the oldest messages begin to be deleted automatically.
-
Maximum message broker throughput for receiving and delivering is about 40 thousand messages per second.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
|
|
required |
Name. May consist of Latin letters and digits and must start with a letter. |
|
|
required |
Role type. Possible values: |
|
|
empty |
Additional role options. Contains a JSON object or list. |
|
|
empty |
Role activity flag. When set to false, the role does not participate in validation and is not started. |
|
|
empty |
Limit on the number of CPU logical cores used. Default: 0 - unlimited. |
|
|
empty |
Default logging level set specifically for the role instance (microservice type). More |
|
|
|
Flag allowing parameter differences in roles of the same group. Default: false - not allowed. |
|
|
required |
Group number. |
|
|
required |
Order of the role instance within the group. |
|
|
|
Object storage operation mode.
|
|
|
global |
Takeover mode switch.
|
|
empty |
List of domain names served by this group. |
|
|
|
Domain distribution group number. Instances with the same value share the domain subtree ( |
Configuration example
Configuration management is performed in an application available to master domain administrators. The application hides the full configuration content, but it is still available through the API.
The configuration contains a section describing all instances of all roles. Parameters are defined for each specific role instance.
{
"name": "broker1",
"roletype": "broker",
"group": 11400,
"order": 1
}