Publisher Mode
When an endpoint uses a persistence store, its publisher send calls communicate outbound messages to the store, as well as to the endpoint’s regular transports. Depending upon application requirements, the publisher send call can also wait for the store to confirm that it has received and stored each message. Different sequences of these subtask elements produce different qualities of service.
Administrators must select the publisher mode that best suits the application’s needs.
| Publisher Mode | Description |
|---|---|
| Store - Send | Highest throughput. Minimal message latency. More robust delivery than regular reliability.
Send the message to the store. Do not wait for confirmation. Send the message on the endpoint’s transports. |
| Store - Confirm - Send | Guarantees delivery in exchange for lower throughput and higher message latency.
If the send call succeeds, then the store guarantees that the appropriate durable subscribers will eventually receive the message. Conversely, if the store operation fails, the send call also fails, and subscribers do not receive the message through direct transports, nor from the store. Send the message to the store. Wait for the cluster to confirm storage. Send the message on the endpoint’s transports. |