Basic message bus service. Suport sync and async message delivery. Point-to-point messaging with round-robin and broadcasting. Message callbacks to delivery results of message processing (for point-to-point only).
Current version: 6.0
To subscribe on message call method addSubscription with string as message destination and instance of the Receiver interface:
MessageBus.addSubscription("Test.Message", (message) -> {
System.out.printf("System message received %s", holder.getTopic());
});or by subscribing to pattern:
MessageBus.addSubscription("Test.*", (message) -> {
System.out.printf("System pattern message received %s", holder.getTopic());
});Pattern matched receivers will be processed after main execution routine and only in async mode.
Bulk subscription possible by addSubscriptions(stringArray, receiver)
Each message contains:
id- unique id of the message;status- status of message processing;topic- message destination (address);headers- string-to-string map for additional data;content- any object (class payload should be familiar to server and subscriber);
Also message can hold response but it's only available to callback implementation. See below.
To fire message:
//Sync, point-to-point, no callback, void delivry, no headers, string content
MessageBus.fire("Test.Empty", "SomeString");
//Sync, point-to-point, no callback, void, headers, no content
MessageBus.fire("Test.Empty2", MessageOptions.Builder.newInstance().header("SomeHeader", "value").build());
//Async, point-to-point, no callback, void, headers, Long content
MessageBus.fire("Test.Empty3", new Long(22), MessageOptions.Builder.newInstanc().header("SomeHeader", "value").async().build());
//Async, point-to-point, callback, void, headers, Long content
MessageBus.fire("Test.Empty4", new Long(22), MessageOptions.Builder.newInstanc().header("SomeHeader", "value").async().callback((response) -> {
System.out.println("Messsage callback after procession!")
}).build());
//Sync call with immediate return
Order created = MessageBus.fireCall("Order.Create", Order newOrder, MessageOptions.Builder.newInstanc().build(), Order.class);- Sync or async mode - message may be processed in the same or in another thread. Sync mode will hang current thread.
- Broadcast or point-to-point - message may be delivered for all subscribers or for just one (round-robin).
- Callback - some logic which will be executed only after message processing. Success not guaranteed. Callback not available for broadcast messages.
- Delivery policy - controls importance of the message:
VOID(set bydeliveryVoid()method in builder, default) - message for testing, bus will not take any action if there is no receivers;CALL(set bydeliveryCall()method in builder) - message for calling remote service and getting response, time-sensetive, bus will throw message if there is no recievers;STORE(set bydeliveryNotification()in builder) - stores messages if there is no receivers at the moment and trying to send them in future;
- Redelivery attempts counter - controls how many times message bus redelivery will try to send this message. After all attempts failed bus will store this message and will not try to redeliver it ever again. By default equals
3. Redelivery can be set only forSTOREdelivery policy;
MessageOptions instance could be reused.
Message bus will try to read bus.json config from resources folder.
Example:
{
"threadPoolConfig": { //Bus thread pool config;
"type": "FIXED_POOL", //Type of the pool: SINGLE_POOL, CACHED_POOL, FIXED_POOL or FORK_JOIN_POOL;
"threadCount": 8 //Number or workers (for async messaging);
},
"bridgeServer": { //HTTP bridge server config;
"httpPort": 4444, //Server port;
"heartbeatRate": 15, //Heart beat rate in seconds;
"crossConnections": true //Enable cross connections;
},
"bridgeClient": { //Config to establish connection to message bus server;
"address": "127.0.0.1", //Address of the server;
"port": 8080, //Port of the server;
"heartbeatRate": 10, //Heart beat rate in seconds;
"tag": "node", //Current node tag, used for node identification;
"additionalSubscriptions": [ //Make additional subscriptions to send on server;
"TEST",
"TEST2",
],
"crossConnectionsReceives": [ //List of topics which sends by current peer;
"Cross.TEST3"
],
"crossConnectionsSends": [ //List of topics whic can be recieved by current peer;
"Cross.TEST4"
]
},
"storage": { //Config for message storage and redelivery
"storageClass": "org.test.MessageStorageImpl", //Path to class to storage implementation;
"storageClassArgs": { //Key-value holder for data needed by strorage to work (optional);
"dbName": "test1",
"dbUser": "user",
"dbPassword": "pass"
}
"redeliveryPeriod": 120, //Period in seconds between redelivery attempts;
"topicPattern": "Test.*", //Pattern of topic to store messages;
"storeCalls": true, //Store messages with delivery policy `CALL`;
"removeProcessed": false //Removes processed messages;
"redeliveryOnlyIfReceiversExists": true //Redelivery attempt will be performed only if there is registered recievers for topic
"groupingScanPeriod": 30 //Period in seconds between scanning for ready to send groupings
"grouping": [ //Message grouping config (list of entries)
{
"singleTopic": "Topic.Single", //Topic to send to single instances
"listTopic": "Topic.List", //Topic to receive list of instances
"maxSize": 100 //Max size of items in storage before sending
"maxTimeInQueue": 300 //Max time in seconds allowed for grouping of a packet of messages
}
]
}
}Central node should config only bridgeServer but other nodes should config both server and client. How it works: central node will establish server and listens for other node subscriptions, when mentioned event happens on central node it will be delivered on subscriber node via HTTP. In order to make node connection reliable also add heartBeatRate on central node server config and on subscriber node client config. Heart beat rate should be at lest slightly larger on server side. Node with obselete heart beat will be disconnected by force.
From 5.0 bus introduces cross connections. It allows to establish direct connections between peers. It should be enabled on central node by flag crossConnections and each peer can specify topic it's needed by crossConnectionsDemand setting. On other side each peer can specify topic it's providing for cross connections by crossConnectionsOffer setting.
Bridge server and client config can be overrided by system properties if needed. Following properties available by now: bridge.server.hearbeat, bridge.server.port, bridge.client.address and bridge.client.port;
During http bridging all headers will be copied, except those which starts with Trans (transient).
From 5.0 message bus supports storing messages for redelivery, grouping and logging. It provides interface MessageStorage for further implementation. There is only one built-in implementation of storage: tk.freaxsoftware.extras.bus.storage.InMemoryMessageStorage but it's not recommened for production use.
Redelivery of messages works only for STORE delivery policy (notifications). Call messages can be only stored (with response).
If you don't want to store some message, just add header Global.Storage.Ignore and storege will ignore it.
Grouping of messages allows to accumulate certain amount of messages and send it in batch. Useful for cases with frequent notifications.
It's possible to subscribe certain method of the class for several messages by using special AnnotationUtil.
Recevier class:
public class OrderService {
@Receive("Org.Test.CreateOrder")
public void createOrder(MessageHolder<Order> orderMessage) {
//logic here
}
@Receive("Org.Test.Delete")
public void deleteOrder(MessageHolder<Order> orderMessage) {
//logic here
}
}To subscribe:
//Class subscription, instance will be created by annotation util
AnnotationUtil.subscribeReceiverClass(OrderService.class);
//Instance subscription
AnnotationUtil.subscribeReceiverInstance(new OrderService(dbConnection));Also AnnotationUtil provides opposite methods to unsubscribe instances and classes.
Library distributed under terms of GNU LGPLv3 license.
© Freax Software 2015-2022