a hard time tracking how
adding the transaction does not incur latency.
On Sep 14, 2022, at 2:03 PM, Nikita Shupletsov
wrote:
Yeah, I agree that there is some overhead because of transactions. but our
tests didn't show any significant impact on the performance.
We use JMS transactions
en to disk,
it would limit the modes in which this could be run (not that it really would make sense
to enable replication for a broker with in-memory only messages), but you couldn't for
example have delayed paging right?.
--
Étienne
On Tue, 13 Sep 2022, at 4:55 PM, Nikita Shupletsov wrote:
Greeti
both writes atomic so that we can preserve consistency.
I would be glad to get any opinion on that.
We are still in the phase of active development and bug fixing, so any
input is welcome!
On 6/10/22 17:15, Nikita Shupletsov wrote:
Greetings.
My name is Nikita Shupletsov. I am a software
Greetings.
My name is Nikita Shupletsov. I am a software development engineer at
Amazon MQ.
I have been working on an Asynchronous Replication plugin for ActiveMQ
“Classic” that was proposed by Étienne Hossack last year:
https://issues.apache.org/jira/browse/AMQ-8354. Étienne published
