Channel patterns

In LowLatencyPubSub, channels are dynamic. You do not need to create them in a database before use. A channel exists while there is at least one active publisher or subscriber.

How to “create” a channel

Simply start using it:

• Writer: publish to a tenant + channel name (example: tenant my-company, channel orders.usd).
• Listener: subscribe to the same tenant + channel (or to a wildcard pattern that matches it).

Coordination between parties

Both sides must agree on tenant and channel name.

Example:

• Writer publishes to alerts.critical.
• Listener A subscribes to alerts.critical -> receives messages.
• Listener B subscribes to alerts.> -> receives messages.
• Listener C subscribes to alerts.info -> does not receive messages.

Naming conventions

Use dots (.) to build a hierarchy:

• Good: sports.football.live, device.sensor-01.temp

Allowed characters for tenant and channel names:

• a-z, A-Z, 0-9, _, -, ~, @, .

Limits (see Limits):

• tenant length: 1..128 bytes
• channel length: 1..256 bytes
• payload length: up to 65535 bytes (~64 KB)