jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig <mdue...@apache.org>
Subject Re: Scalability of JCR observation
Date Tue, 16 Apr 2013 09:49:36 GMT


On 15.4.13 9:32, Bertrand Delacretaz wrote:
> Hi,
>
> On Fri, Apr 12, 2013 at 3:35 PM, Michael Dürig <mduerig@apache.org> wrote:
>> An implementation approach for backward compatible observation is to use a
>> commit hook to record the required changes to a journal (e.g.
>> /jcr:system/rep:observation). Observation listeners would then later
>> generate the observation events by scrapping that journal asynchronously...
>
> This sounds a lot like a distributed message queue...

Right.

>
>> ...A somewhat open question is how this should work across the cluster...
>
> So I'm wondering if using an existing distributed message queue
> service (ActiveMQ/RabbitMQ etc) would help implement this. IIUC this
> is only a problem in very large Oak setups, so having to install
> additional components might not be an issue.

Yes I think we can do that. In a first step I'd like to have an 
implementation entirely internal to Oak so we can validate it against 
our basic use cases. Further down the line we can abstract over the 
underlying queueing mechanism such that other backends could be pugged in.

Michael

>
> -Bertrand
>

Mime
View raw message