Hi,
As the API somewhat stabilised, I opened a PR with a basic implementation
of journaled event API
https://github.com/apache/aries-journaled-events/pull/17
In addition to being basic, it is also barely tested for now.
I plan to improve this implementation via more PRs towards the following:
* Making a more efficient use of partitions using configurable keys instead
of hardcoding partitions (currently the code only leverage the partition 0
and does not support keys)
* Extend test coverage to include Kafka specifics such as topic partitioning
* Extend test coverage by allowing to run the test suite currently in the
journal event in-memory implementation
* Add/evaluate a simple caching strategy (potentially to be shared with the
Mongo implementation in a org.apache.aries.events.common module)
Review/merge welcome :-)
Regards,
Timothee
Le mer. 2 janv. 2019 à 11:47, Timothee Maret <tma...@apache.org> a écrit :
> Thanks JB!
>
> Using Github PRs make sense to me. I have started working in this branch
>
>
> https://github.com/tmaret/aries-journaled-events/tree/kafka-implementation
>
> It is only a start to see how the API can be implemented.
> I will open a first PR when the API and implementation has stabilised a
> bit and add tests afterwards.
>
> Regards,
>
> Timothee
>
> Le lun. 31 déc. 2018 à 06:00, Jean-Baptiste Onofré <j...@nanthrax.net> a
> écrit :
>
>> Hi Timothee,
>>
>> welcome !
>>
>> I would be happy to work with you on this implementation.
>>
>> Now that we have the repo ready, I propose to work with PullRequest on
>> github. It would allow us to review and be updated about the changes.
>>
>> Regards
>> JB
>>
>> On 30/12/2018 22:40, Timothee Maret wrote:
>> > Hi,
>> >
>> > I noticed that a repository for the event journal sub project [0] was
>> > created and that a first draft of the API had been pushed. This is great
>> > news!
>> >
>> > I would like to offer to contribute to this sub project but first, let
>> me
>> > introduce myself to the Aries developer community.
>> >
>> > My name is Timothee Maret, I live in Switzerland and have worked for
>> Adobe
>> > in Basel for nearly 9 years. I focus on the development and cloud
>> > deployment of Adobe Experience Manager. I am an Apache committer on the
>> > Sling project where I mostly contribute to Sling Content Distribution
>> > evolution. For the last 2 years I have led the design/implementation of
>> a
>> > content replication mechanism able to support AEM scalability
>> requirements
>> > in the cloud.
>> >
>> > The replication design follows the event sourcing pattern and is
>> currently
>> > implemented on top of Apache Kafka. Kafka is a perfect fit for this
>> design.
>> > However, as we may end up leveraging an alternative backend for non
>> > technical reasons, we intend to guarantee the design portability by
>> > leveraging the API/spec as soon as it is available. A second class of
>> use
>> > cases for the API/spec in AEM would be every implementation involving
>> > components decoupled via events and requirements for processing
>> guarantees.
>> >
>> > I am proposing to start contributing to this sub project by providing an
>> > implementation on top of Apache Kafka.
>> >
>> > If this contribution is welcomed by the Aries community, please let me
>> know
>> > if I should start with filling a JIRA in the ARIES tracker or somewhere
>> > else!
>> >
>> > Regards,
>> >
>> > Timothee
>> >
>> > [0]
>> >
>> https://lists.apache.org/thread.html/47c4c103c026ad57887796d400c6ae6004fa8346346d8b4321ceceee@%3Cdev.aries.apache.org%3E
>> > [1] https://github.com/apache/aries-journaled-events
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
