Show TOC

RTMF ServicesLocate this document in the navigation structure

Use

RTMF services listen for specific messages sent directly to them, and then perform tasks based on the message and its parameters.

For example, a bulletin board could implement several services for receiving messages from users - to post messages, to get the latest messages, to configure the bulletin board. When each service receives a message, it checks the message's parameters, performs some logic, and publishes events to inform all subscribing clients of any updates.

There are several types of services:

  • Sync Service: Any message sent to a sync service is sent synchronously, meaning the calling application or service gets an instance of the service, sends the message to it, and waits for a reply.

    The message is sent only to the service on the current cluster node.

    A bulletin board could implement a sync service to enable a user to get the latest posts for a specific topic. The client application waits to receive the list of posts.

  • Topic Service: Any message sent to a topic service is sent asynchronously, meaning the calling application or service sends the message to the RTMF server (to dispatch it to the service) and does not wait for a reply.

    The message is sent to the service on all cluster nodes.

    A bulletin board could implement a topic service to enable a user to configure settings that must be done on each cluster node. The client application does not wait for a reply.

  • Queue Service: Any message sent to a queue service is sent asynchronously, meaning the calling application or service sends the message to the RTMF server (to dispatch it to the service) and does not wait for a reply.

    The message is sent to the service on only one of the cluster nodes. There is no way to know which service will receive the message.

    A bulletin board could implement a queue service to enable a user to post to the bulleting board. The service receives the message, and then alerts all subscribers to the new post by publishing an event. The client application does not wait for a reply.

This section describes the following tasks: