public interface ITopic<E> extends DistributedObject
Messages are ordered, meaning that listeners(subscribers) will process the messages in the order they are actually published. If cluster member M publishes messages m1, m2, m3...mn to a topic T, then Hazelcast makes sure that all of the subscribers of topic T will receive and process m1, m2, m3...mn in order.
Since Hazelcast 3.5 it is possible to have reliable topics. Normally all topics rely on the a shared eventing system and
shared threads. With Hazelcast 3.5 it is possible to configure a topic to be reliable and to gets its own
Ringbuffer
to store events and to gets its own executor to process events. The events
in the ringbuffer are replicated, so they won't get lost when a node goes down.
Modifier and Type | Method and Description |
---|---|
String |
addMessageListener(MessageListener<E> listener)
Subscribes to this topic.
|
LocalTopicStats |
getLocalTopicStats()
Returns statistics about this topic, like total number of publishes/receives.
|
String |
getName()
Returns the name of this ITopic instance.
|
void |
publish(E message)
Publishes the message to all subscribers of this topic.
|
boolean |
removeMessageListener(String registrationId)
Stops receiving messages for the given message listener.
|
destroy, getPartitionKey, getServiceName
String getName()
getName
in interface DistributedObject
void publish(E message)
message
- the message to publish to all subscribers of this topicTopicOverloadException
- if the consumer is too slow (only works in combination with reliable topic)String addMessageListener(MessageListener<E> listener)
listener
- the MessageListener to addNullPointerException
- if listener is null
boolean removeMessageListener(String registrationId)
registrationId
- ID of listener registrationtrue
if registration is removed, false
otherwiseLocalTopicStats getLocalTopicStats()
Copyright © 2018 Hazelcast, Inc.. All rights reserved.