Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
The moose likes Java in General and the fly likes JMS broker outside firewall Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Java » Java in General
Bookmark "JMS broker outside firewall" Watch "JMS broker outside firewall" New topic
Author

JMS broker outside firewall

surlac surlacovich
Ranch Hand

Joined: Mar 12, 2013
Posts: 296

I've got general question regarding JMS usage.
Why is it good practice to put JMS broker outside of firewall, while all the other sub-systems stay behind firewall. What benefit from that, JMS has ability to send messages through firewall securely?

Quote from WSO2 ESB + Qpid article:
You may wish to send messages from outside a firewall to a server inside. You could connect an ESB within the firewall to a Message Broker running outside the firewall (for example on Amazon EC2).
Henry Wong
author
Sheriff

Joined: Sep 28, 2004
Posts: 18765
    
  40

surlac surlacovich wrote:I've got general question regarding JMS usage.
Why is it good practice to put JMS broker outside of firewall, while all the other sub-systems stay behind firewall. What benefit from that, JMS has ability to send messages through firewall securely?

Quote from WSO2 ESB + Qpid article:
You may wish to send messages from outside a firewall to a server inside. You could connect an ESB within the firewall to a Message Broker running outside the firewall (for example on Amazon EC2).



Well, there is a use-case not in context here... Quite frankly, for a majority of cases, where the JMS broker is doing messaging between applications within the same datacenter (heck, even in the same subnet), the JMS broker should be with the applications.

There is no general practice to always put the JMS broker outside the firewall.

Henry


Books: Java Threads, 3rd Edition, Jini in a Nutshell, and Java Gems (contributor)
surlac surlacovich
Ranch Hand

Joined: Mar 12, 2013
Posts: 296

Oh, I see, thanks.
I think by this case with moving the broker to Amazon EC2 they meant "If you want to move the broker to really-really fast machine and it is outside of firewall you can do that".
Can the JMS broker be a performance bottleneck (so it must be moved to a powerful machine)? I've heard that Qpid implementation of the broker is really fast.
surlac surlacovich
Ranch Hand

Joined: Mar 12, 2013
Posts: 296

surlac surlacovich wrote:
Can the JMS broker be a performance bottleneck (so it must be moved to a powerful machine)?

Also, some providers use NoSQL which is extremely fast.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JMS broker outside firewall