sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Egli (JIRA)" <>
Subject [jira] [Commented] (SLING-6745) kafka-based sling.event.api implementation
Date Thu, 30 Mar 2017 15:18:41 GMT


Stefan Egli commented on SLING-6745:

bq. As a summary : I think it doesn't make sense to reuse the MoM-based Jobs API - but it
might make sense to use the MoM API/SPI.
I'm taking that back for now. Perhaps it's feasible to build ontop of mom/jobs/core I have
to see. I think where my concern is that it could be confusing to have 2 'job apis' in the
same deployment and that the two might interfere. But 'building ontop of mom/jobs/core' could
also be done by embedding it - thus not really exposing its API.

> kafka-based sling.event.api implementation
> ------------------------------------------
>                 Key: SLING-6745
>                 URL:
>             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|]).
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

View raw message