Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of mreutegg@adobe.com designates
 64.18.1.185 as permitted sender)
From: Marcel Reutegger <mreutegg@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Date: Mon, 10 Sep 2012 11:33:18 +0100
Subject: process boundaries
Thread-Topic: process boundaries
Thread-Index: Ac2PPNRkiWD/h+7BQTidX/m/iywd5A==
Message-ID: 
 <9C0FC4C8E9C29945B01766FC7F9D389816FE0B2083@eurmbx01.eur.adobe.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

hi all,

while looking through the oak code and also in light of the
recent MongoDB based MicroKernel, I was wondering where
the process boundaries are. right now with the maven build
everything runs in the same process, which is one possible
deployment option. I guess as soon as we have some
alternative MicroKernel implementation that scales well, we
will probably also think about scaling the application on top
of oak. the most obvious solution is to just run the application
multiple times in separate processes and they all connect
to the oak repository.

there's existing information on that topic, like the stack=20
with the different layers [0], however it doesn't talk about
where the process boundaries are and where we'd need
a protocol (except for the top level protocols to access=20
the content through JCR or the Oak API directly).

so, the question I have is basically about oak-core. is it
intended and designed to run in multiple processes and
access a single MicroKernel instance? that way an application
running in multiple processes would embed an oak-core,
which talks to the MicroKernen. Or is it rather intended
that oak-core runs in a single process and all clients
connect to that single instance?

regards
 marcel

[0] http://wiki.apache.org/jackrabbit/OakComponentStructure