First of all sorry for my poor english. Let's get to the point, I am planing to create a system that will make use of
MDB but I don't want to use any other part of EJB3 specification. I am considering using Glassfish as my
EJB container. The web part that will be sending messages to message brokers will be created and deployed on Tomcat.
Is it overkill to use Glassfish + MDB only to just handle messages from Message brokers without doing anything else like session beans or JPA?
Will there be any performance hit? Because the volume of messages that the MDBs must handle is substantial. (may be
more than a million of messages on some period of time)
I decided to use this pair because I learned them when I prepared for the SCBCD exam and I realize that
it is better to use the tools that I am more familiar rather than learning a new thing which is more popular (In my opinion) like
JMSTemplate of Spring. In addition, I love the idea of MDB for pooling beans when handling each message.
If there is an alternative or any good suggestions, please let me know.