When to Use Persistence with Java Messaging and Queuing Systems

I am doing research in the field of trade (Java) Messaging and Queuing for the upcoming reorganization of the background infrastructure for the main web application (on Amazon EC2 Cloud, x-large copies). I am currently evaluating ActiveMQ and RabbitMQ.

The plan is to have 5 different queues, one of which is a dead letter queue. The number of messages sent per day will be anywhere between 40 and 400 KB. Since I plan that the content of the message is a pointer to the location of the XML file in the data warehouse, I expect the messages to contain about 64 bytes. However, for evaluation purposes, I would also like to consider sending raw XML to messages with an average file size of 3 KB.

My main questions: when / how many messages should be continued daily? Does it make sense to save all messages, taking into account the amounts indicated by me above? I know that saving will slow performance, maybe a lot. But, without stopping, a large RAM is used. What would you recommend?

In addition, I know that there is a lot of information on the Internet about ActiveMQ (JMS) and RabbitMQ (AMQP). I have done a lot of research and testing. It seems that any implementation will fit my needs. Given the above information (file sizes and number of messages), can someone please indicate the reason for using a particular provider that I may have missed?

Thank!

+5
source share
3 answers

/ ? , ?

JMS , . / , , JMS ( ) ( )

, , , . , , . ?

, . () () ( / )... JMS

, , ActiveMQ (JMS) RabbitMQ (AMQP). . , . ( ), - , , ?

ActiveMQ . , Apache Camel,

+2

. , . , . , , . , , .

, , , .

, IBM WebSphere MQ. . JMS, API .

+3

ActiveMQ - JMS , , , TIBCO EMS , , Solace.

JMS , . , , , , .

, (: CodeStreet), "ReplayService JMS". JMS ( WebSphere MQ) . MsgID, . , XML- ReplayServer, globalMsgID . , ?

globalMsgID, ReplayServer, .

But, on the other hand, the 400K * 3KB XML message should be easily executable for ActiveMQ or others. In addition, you must compress your XML messages before sending.

0
source

All Articles