Topic Endpoints

A topic endpoint attracts messages published to a topic for which the topic endpoint has a matching topic subscription. The topic subscription for the topic endpoint is specified in the client request to bind a Flow to that topic endpoint.

Topic endpoints offer fewer options than queues and can subscribe to only one topic but they are helpful for some use cases.

Topic endpoints can be used in a pub/sub model. They are equivalent to durable topic subscriptions in Java Message Service (JMS).

A durable topic endpoint has an access type, which determines how messages are delivered when multiple consumer flows are bound to it. Topic endpoints can be assigned one of the following access types:

• Exclusive—specifies that only one client can be active on the topic endpoint. If other consumers attempt to bind and the max-bind-count value of the topic endpoint is not exceeded, they will bind, but remain inactive until the active consumer is unbound and a new active consumer is chosen from the topic endpoint's inactive consumers. Exclusive topic endpoints always deliver messages in the order they are received.
• Non-exclusive—specifies that all bound flows are able to receive messages, and when multiple flows are bound to a non-exclusive topic endpoint, they receive messages in a round-robin fashion.

For information about configuring topic endpoints using the Solace CLI, see Configuring Topic Endpoints.

For more information about configuring topic endpoints in PubSub+ Broker Manager, see Configuring Topic Endpoints for PubSub+ Cloud or Configuring Topic Endpoints for software event brokers and appliances.

For more information about collecting topic endpoint data, see Viewing Endpoint Messaging Data for PubSub+ Cloud or Viewing Endpoint Messaging Data for software event brokers and appliances.