Jackrabbit 3: architectural changes

[Jukka Zitting <ju...@gmail.com>]

Hi,

Thanks for all the responses to the repository requirements thread
(keep 'em coming)! That's very valuable information when we start
looking deeper at the architectural changes and tradeoffs ahead of us.

The main concepts of the current Jackrabbit 1.x/2x. architecture date
back to almost a decade ago. During that time we've learned a lot more
about how content repositories are best used and implemented, and also
the underlying hardware technology has changed dramatically during
this time. Now that we're done implementing the new features and
changes for JCR 2.0, it's a good time to discuss what we can and
should make to modernize the Jackrabbit architecture.

Instead of a single huge thread, I'm going to fire up a number of
parallel threads on specific ideas related to this. Feel free to add
your own ideas to the mix. Let's use the subject prefix [jr3] to make
these design threads easy to identify.

BR,

Jukka Zitting

Re: Jackrabbit 3: architectural changes

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Wed, Feb 17, 2010 at 5:44 PM, Jukka Zitting <ju...@gmail.com> wrote:
> BTW, this doesn't mean that we're going to implement everything at
> once. Instead, once we have better consensus on what can and should be
> done on the various ideas, I'd like to build an incremental roadmap
> from Jackrabbit 2.1, 2.2, ... to 3.0 [...]

As a first step to such consolidation I started collecting pointers to
all these threads on http://wiki.apache.org/jackrabbit/RoadMap

BR,

Jukka Zitting

Re: Jackrabbit 3: architectural changes

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Wed, Feb 17, 2010 at 4:11 PM, Jukka Zitting <ju...@gmail.com> wrote:
> [...] Now that we're done implementing the new features and
> changes for JCR 2.0, it's a good time to discuss what we can and
> should make to modernize the Jackrabbit architecture.

BTW, this doesn't mean that we're going to implement everything at
once. Instead, once we have better consensus on what can and should be
done on the various ideas, I'd like to build an incremental roadmap
from Jackrabbit 2.1, 2.2, ... to 3.0 over which we can implement these
improvements while still maintaining sufficient backwards
compatibility.

BR,

Jukka Zitting

Re: Jackrabbit 3: architectural changes

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Thu, Feb 18, 2010 at 5:07 AM, Justin Edelson <ju...@gmail.com> wrote:
> Just to clarify, you're talking about Jackrabbit 3, not JCR 3, right?

Yes.

BR,

Jukka Zitting

Re: Jackrabbit 3: architectural changes

[Justin Edelson <ju...@gmail.com>]

Jukka-
Just to clarify, you're talking about Jackrabbit 3, not JCR 3, right?

Thanks,
Justin

On 2/17/10 10:11 AM, Jukka Zitting wrote:
> Hi,
> 
> Thanks for all the responses to the repository requirements thread
> (keep 'em coming)! That's very valuable information when we start
> looking deeper at the architectural changes and tradeoffs ahead of us.
> 
> The main concepts of the current Jackrabbit 1.x/2x. architecture date
> back to almost a decade ago. During that time we've learned a lot more
> about how content repositories are best used and implemented, and also
> the underlying hardware technology has changed dramatically during
> this time. Now that we're done implementing the new features and
> changes for JCR 2.0, it's a good time to discuss what we can and
> should make to modernize the Jackrabbit architecture.
> 
> Instead of a single huge thread, I'm going to fire up a number of
> parallel threads on specific ideas related to this. Feel free to add
> your own ideas to the mix. Let's use the subject prefix [jr3] to make
> these design threads easy to identify.
> 
> BR,
> 
> Jukka Zitting