[SLING-6745] kafka-based sling.event.api implementation

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Won't Do
• Assignee: Stefan Egli
• Reporter: Stefan Egli
• Created: 29/Mar/17 12:05
• Updated: 07/Aug/17 08:13
• Resolved: 13/Apr/17 12:39

Description

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.

Issue Links

• is blocked by: SLING-6739 split sling.event into event.api and event.resource (was: event.impl)