Need help in design
Rizwan Mohammad
Ranch Hand
Posts: 445
posted 5 years ago
Hi,
We have few applications in our enterprise one being the master. We have to send nearly one hundred thousand messages daily from master application to all dependent application using messaging service (via Webspher Message Broker) and we need to get response after successful consumption of messages for logging purpose.
Can you please suggest me the best design/architecture for this solution.
Note: Master application is developed in j2ee and hosted in websphere application server.
Thanks in advance for your suggestions.
We have few applications in our enterprise one being the master. We have to send nearly one hundred thousand messages daily from master application to all dependent application using messaging service (via Webspher Message Broker) and we need to get response after successful consumption of messages for logging purpose.
Can you please suggest me the best design/architecture for this solution.
Note: Master application is developed in j2ee and hosted in websphere application server.
Thanks in advance for your suggestions.
Rizwan
SCJA, SCJP, SCWCD, SCBCD, SCDJWS.
posted 5 years ago
ESB's like Mule are being used in the industry for such jobs these days.
They have elaborate message routers and frameworks.
They have elaborate message routers and frameworks.
Anrd
"One of the best things you could do is to simplify a larger application into a smaller one by reducing its process and complexity - Fowler"
posted 3 years ago
Seems as though the OP has an ESB already. What advantage do you see for the OP to switch from his current ESB to Mule ?
Aniruddh Joshi wrote:ESB's like Mule are being used in the industry for such jobs these days.
They have elaborate message routers and frameworks.
Seems as though the OP has an ESB already. What advantage do you see for the OP to switch from his current ESB to Mule ?
posted 3 years ago
It looks like you want to have a Request/Reply pattern. Master sends the request and after a short time, processes replies, marking the requests complete in a database, and perhaps sending an output message to Logger. Have you considered this already ? If so, what did you see as the drawback ?
Rizwan Mohammad wrote:Hi,
We have few applications in our enterprise one being the master. We have to send nearly one hundred thousand messages daily from master application to all dependent application using messaging service (via Webspher Message Broker) and we need to get response after successful consumption of messages for logging purpose.
Can you please suggest me the best design/architecture for this solution.
Note: Master application is developed in j2ee and hosted in websphere application server.
Thanks in advance for your suggestions.
It looks like you want to have a Request/Reply pattern. Master sends the request and after a short time, processes replies, marking the requests complete in a database, and perhaps sending an output message to Logger. Have you considered this already ? If so, what did you see as the drawback ?
