[jira] [Commented] (SLING-6745) kafka-based sling.event.api implementation

["Konrad Windszus (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-6745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116227#comment-16116227 ] 

Konrad Windszus commented on SLING-6745:
----------------------------------------

For the record, the modules can be found now `contrib/commons/mom` (https://github.com/apache/sling/tree/trunk/contrib/commons/mom).

> kafka-based sling.event.api implementation
> ------------------------------------------
>
>                 Key: SLING-6745
>                 URL: https://issues.apache.org/jira/browse/SLING-6745
>             Project: Sling
>          Issue Type: New Feature
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>
> In job handling to scale for larger deployment it is essential to be able to execute a job outside of the local instance. This can be in another instance in the same cluster (ie when ontop of documentMk) or outside of the cluster (in AEM eg via [offloading|https://docs.adobe.com/docs/en/aem/6-2/deploy/configuring/offloading.html]). In both cases Sling Event (Resource) stores the job in the repository (/var/eventing/jobs).
> It could be useful to have another variant of job execution that is managed entirely outside of the repository. With SLING-5645 a new API was created to support messaging-based implementations that would fit in this category as they map a job to a (one or a few) message(s). 
> This new SLING-5645 Job-API is not entirely compatible with sling.event.api though.
> This ticket is to track an effort to provide a messaging-based implementation for sling.event.api - namely for Kafka. The goal is to become a drop-in replacement of sling event without much need for change on the user side of the sling.event.api.
> This might not right away become part of sling, but might start off in the contrib section - to underscore that it's not something supported, at least as of yet.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)