3 Replies Latest reply on Apr 11, 2011 6:17 AM by ataylor

Message Driven Beans as anti-pattern

esteve Apr 8, 2011 3:54 AM

Hi,

After reading the great HornetQ documentation I have found that at the begining they recommend the usage of MDB when using messaging in JEE environement, but at the end of the documents, in the anti-patters section they write:

Don't use Message-Driven Beans for the sake of it. As soon as you start using MDBs you are greatly increasing the codepath for each message received compared to a straightforward message consumer, since a lot of extra application server code is executed. Ask yourself do you really need MDBs? Can you accomplish the same task using just a normal message consumer?

I am not very prone to EJBs and I agree with the anti-pattern, but there is a complete section on this matter.

Any opinion?

Don't use Message-Driven Beans for the sake of it. As soon as you start using MDBs you are greatly increasing the codepath for each message received compared to a straightforward message consumer, since a lot of extra application server code is executed. Ask yourself do you really need MDBs? Can you accomplish the same task using just a normal message consumer?Don't use Message-Driven Beans for the sake of it. As soon as you start using MDBs you are greatly increasing the codepath for each message received compared to a straightforward message consumer, since a lot of extra application server code is executed. Ask yourself do you really need MDBs? Can you accomplish the same task using just a normal message consumer?

1. Message Driven Beans as anti-pattern

ataylor Apr 8, 2011 4:22 AM (in response to esteve)

I'm not really sure what your asking but all its not really an anti pattern per se, all we are saying is that if you are going to use MDB's be mindful that there is a over head for transaction coordination, security and other JCA stuff.
Actions
2. Message Driven Beans as anti-pattern

esteve Apr 11, 2011 6:10 AM (in response to ataylor)

Ok, it is clear to me that what you are saying is: Use MDB's only if you require EJB's features otherwise you normal message consumers like JMS.
Actions
3. Message Driven Beans as anti-pattern

ataylor Apr 11, 2011 6:17 AM (in response to esteve)

thats about the jist of it, people tend to use MDB's (and spring jms etc) because they are simple to develop and configure etc, without any thought as to the overhead of using them
Actions

Go to original post