architecture - Way to communicate between backend server ? -


i have work on 3 distinct applications instead of big one. question : "can jms used communicate between different servers (wildfly)" ?

this way can add more servers second application if see take longs process. here simple exemple 15 servers. 5 first app take data , them. 5 second app calculate , last application format them , store them second db.

if second app takes long, able add 3 servers on fly , let them connect first jms q , second jms q.

maybe other suggestion how build ?

thanks

enter image description here

this pretty standard messaging.

might depend on jms server, if use queues, each server should able consume individually , message process.

the bigger issue going design of applications. need stateless message can picked server in order , processed without regard else happening. [of course, if there's shared back-end data provider shared among servers, provide context.]

another issue going transactionality , recovery. if message picked server but, whatever reason, server can't process message, have transaction manager allows roll or have put on queue (either originating 1 or new one) yourself? , happens if message continues fail whatever reason, mean (especially if there additional messages should processed after failed message).

so need consider applications' architecture, otherwise messaging sound solution.


Comments

Popular posts from this blog

Delphi XE2 Indy10 udp client-server interchange using SendBuffer-ReceiveBuffer -

Qt ActiveX WMI QAxBase::dynamicCallHelper: ItemIndex(int): No such property in -

Enable autocomplete or intellisense in Atom editor for PHP -