How does sending a large message via Active MQ compare to a solution where the client just saves the data contents to a database and only send some sort of locator id to the recipeints. The recipients which are aware of the database can then retrieve the contents by the locator ID. Is this effectively the same as the ActiveMQ broker storing the message and clients retrieving them? Or is the database approach more efficient with respect to memory usage, etc?
In general, is sending such large messages over a (JMS) message bus legitimate use case? Can you describe some use cases where they are doing so in production. When dealing with such large amounts of data, I normally think ETL. Sanjiv On 7/6/06, nlif <[EMAIL PROTECTED]> wrote:
Thanks a lot for all your answers, James. It seems all our requirements can be met using ActiveMQ. As for feedback on the site: I have been keeping an eye on ActiveMQ for about 6 months now, and there is a definite improvement in the amount and quality of the on-line documentation. Furthermore, I am constantly impressed by the activeMQ team's positive and helpful responses when posting questions/problems in the user forum. Just out of curiosity, is there any intention of publishing a book? "ActiveMQ in Action" has a nice sound to it, wouldn't you say :-) Naaman -- View this message in context: http://www.nabble.com/Duplicating-Large-Messages-tf1880194.html#a5198671 Sent from the ActiveMQ - User forum at Nabble.com.
