jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Mueller <muel...@adobe.com>
Subject Re: writing a new MK, guidelines
Date Wed, 06 Nov 2013 11:01:43 GMT

Implementing a complete MK is quite some work. It depends what you want to
do with it. If you want to quickly implement a storage backend that you
can test with Oak, then it might be easier to implement a storage backend
for one of the existing MKs (for example the MongoMK, or the
MicroKernelImpl). Which one matches best depends on the features you like
to have (clustering, concurrency,...) and the storage you have (key-value
store, document store,...).


On 11/6/13 11:31 AM, "Tommaso Teofili" <tommaso.teofili@gmail.com> wrote:

>Hi all,
>out of curiosity, I was wondering if there's any guideline other than
>following the API on writing a new MK implementation.
>What one should start with, design concepts, experience on known dos,
>donts, caveats, etc.
>In the past I wanted to play with it a bit but never had time to do
>anything there however that may be a useful information (if anything like
>that exists) to share.

View raw message