Hello, I am looking into the creation of an audit log node structure in a Sling-managed Jackrabbit repository. This structure might grow quickly to contain many nodes. As writing these nodes one-by-one can be costly, I'd like to avoid doing the writing to the repository synchronously. Instead, I'd like to dispatch an audit event to some sort of message bus, which is consumed by a dedicated Sling process that creates the nodes.
This message bus may be synchronous or asynchronous, but ideally it would have some failure recovery mechanism to be sure that all dispatched audit events will be persisted to the repository, eventually. Does something like this already exist in Sling? Cheers Lukas
