On Tuesday 20 October 2015 21:23:49 Carsten Ziegeler wrote: > Am 20.10.15 um 21:06 schrieb Oliver Lietz: > > On Monday 19 October 2015 14:46:05 Carsten Ziegeler wrote: > >> Hi, > > > > hi, > > > >> with https://issues.apache.org/jira/browse/SLING-4751 we have a new API > >> for dealing with change events on both sides, the reporting part and the > >> client using the events. The basic idea is to have a more scalable > >> approach. > >> > >> Now, if we think of large scalable systems, there is one thing that is > >> not very optimal: dealing with external observation events. Obviously > >> sending all observation events to all potentially interested parties is > >> not really cheap. > >> There are additional things, like e.g. Oak is not providing the commit > >> info for external events. Therefore the user of the change is unknown. > >> With other resource providers, like mongo, cassandra etc. there is not > >> even an infrastructure to send external change events across instances. [...] > >> With the move to the new observation api we now have the chance to come > >> up with the best solution. We just need to figure out, what this is. > >> > >> Thoughts? > > > > have you considered something like Apache Ignite or Apache Kafka? > > Can you elaborate on how this could help?
Sure. These frameworks are build for handling distributed events in clustered setups. As Bertrand already pointed out, they could be used as our infrastructure for external – or remote – events. Maybe even for local events. I haven't looked at Michael's POC so far, but we should coordinate with the Oak team if they are looking for something similar. Though I would start with evaluating Ignite as it offers additional features (caching, clustering, leader election - where we obviously have demand) which could be useful in Sling. Btw, is there any progress at OSGi's RFP 158 Distributed Eventing? Regards, O. > Regards > Carsten > > > Regards, > > O. > > > >> Regards > >> Carsten
