This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
One or more queue?
I'm design a system in which I call some external webservices.
I wish to log any webservice response in my database for logging purpose.
So in order to don't slow down the system with logging work (INSERT QUERY etc.), I take decision about using a message driven bean in order to log the response writing it in database.
So, I call webservice, then the response DTO is send to queue, then in asynchronous mode the mdb write it on db.
I use approximately 7-8 webservice, each one with different response object.
The question is..I have to make one queue for response type, or a single queue that manage all the response type?!
I wish to obtain in reply some opinion or design pattern about this.
thanks in advance
Article and example (english and italian) about
[Java EE, Hibernate, EJB, Servlet, JSP, WebService, Glassfish, Java ME etc]
<a href="http://programmaremobile.blogspot.com " rel="nofollow">http://programmaremobile.blogspot.com</a>
I think you will probably use a single queue here, but without any other work, you will find that you will need to write custom code for each of the types of response objects when you want to convert each into a JMS Message to post.