activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Edstrom <seij...@gmail.com>
Subject Re: Persistence delay in JDBC Master/Slave approach
Date Thu, 28 Oct 2010 18:20:52 GMT
The pages outlining HA are pretty clear on the concept.
If you want a hybrid approach of persisting things yourself, sure, divert the messages, use
camel.
Anything in RAM is gone if you lost that node, anything in "transit" is lost.


On Oct 28, 2010, at 12:18 PM, kseelam wrote:

> 
> Hi All
> 
> We have a situation where we want to Persist the messages in the permanent
> DB but first temporarily store in the memory(or similar) and 'some time
> later' persist the messages in the DB. So that client don't wait till the
> messages are written in the DB.
> 
> We understand the Journal concept. But we want to achieve this in
> Master/Slave approach by using one Mysql DB for HA.  Other threads suggest
> Journal does not work well for Master/Slave approach. So its limitation. 
> 
> We really struck of choosing the best approach.
> 
> Just wondering any other workarounds or suggestions. 
> 
> Thank you all.
> -- 
> View this message in context: http://activemq.2283324.n4.nabble.com/Persistence-delay-in-JDBC-Master-Slave-approach-tp3017852p3017852.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Johan Edstrom

joed@opennms.org

They that can give up essential liberty to purchase a little temporary safety, deserve neither
liberty nor safety.

Benjamin Franklin, Historical Review of Pennsylvania, 1759






Mime
View raw message