Hi Dirk, The service would expose distribution queues via a REST API. Primary consumers will be Sling Content Distribution agents. The API could eventually be used for other use cases but it's not an immediate goal.
Regards, Timothee Le jeu. 9 avr. 2020 à 15:52, Dirk Rudolph <dirk.rudo...@netcentric.biz> a écrit : > Hi Timothee, > > that sounds great, indeed. Is a Sling as source, the Kafka journal as > messaging system and anything like solr as sink, what you have in mind? > > In the past I tried to implement a distribution with Solr as sink, which > unfortunately was more complicated than I thought initially. > > Regards, > Dirk > > > > On 9 Apr 2020, at 15:06, Timothee Maret <tma...@apache.org> wrote: > > > > Hi, > > > > At Adobe we rely on journal based content distribution [0] for AEM in the > > cloud. We would like to explore with the idea of providing content > > distribution as a service. > > > > We are planning to work on that service under the Sling umbrella and > think > > of leveraging the existing journal based content distribution bundles > [1]. > > This effort will likely require refactoring the code and the bundle > > dependencies. We will strive to keep backward compatibility and plan to > > evaluate the feasibility in branches for the existing modules. > > > > If the Sling community is fine with this, we'd start prototyping the > > service in the Sling whiteboard [2]. > > > > Regards, > > > > Timothee > > > > [0] > https://github.com/apache/sling-org-apache-sling-distribution-journal > > [1] > > > https://github.com/apache/sling-aggregator/blob/master/docs/groups/distribution.md > > [2] https://github.com/apache/sling-whiteboard > >
