A MigratoryData message is composed of various pieces of information which are listed below. The
content properties are mandatory and are required to be non-empty strings, while the other properties have default
values that are either empty strings or are indicated in bold below.
||any valid subject||the subject of the message|
||any UTF-8 string||the content of the message|
||any UTF-8 string||the ID of the message|
||indicate whether or not the message should be/was retained by the server|
||indicate whether or not the message should be/was compressed|
||indicate the quality of the service of the message|
||the type of the message|
||any valid subject||publishers can attach a
MigratoryData client API provides methods to create messages from application-specific data, publish messages, and retrieve the application-specific data from messages when received by subscribers.
A subscriber will receive real-time messages labeled with
update message type. If the MigratoryData cluster is configured
to use Guaranteed Message Delivery as quality of the service (QoS) and the subscriber reconnects after a failure,
any messages that were missed during the recovery period for the subjects it subscribed to will be obtained upon reconnection to the
cluster. These missed messages will be labeled with
recovered message type. The other message types
detailed in the section History.
replySubjectproperty within MigratoryData publish/subscribe model, it is possible to implement a request/reply interaction. This interaction occurs over persistent connections and can serve as a more scalable and lower latency alternative to RESTful communication, as demonstrated here.