You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Patrick Herber <pa...@ticino.com> on 2006/10/28 16:38:22 UTC

JCR for everything (...or still some use of RDB)?

Hello,
 
I'm currently working at the design of a web collaboration application
(things like knowledge-, time-, projects-, ... management) and I tought it
would be very interesting to use jackrabbit for storing the content, since
many features I need, like versioning, observation, access control, ...,
come fast "out-of-the-box".
 
Now, I'm new to Content Repositories and also to jackrabbit and I'm
wondering: it's suggested to save everything in the content repository or,
for some parts, of the application data is still prefered the use of a
relational DB?
I'm thinking, using the example of my project, about relationships between
the different "content-objects", or about ratings and tags, which users can
give to these objects.
 
Thanks a lot for your suggestions.
 
Best regards,
Patrick

Re: JCR for everything (...or still some use of RDB)?

Posted by Miro Walker <mi...@gmail.com>.
Something to consider here is whether you will ever need to have
transactions that update the stuff you're thinking of putting in the
DB and the content in your JCR repo at the same time. This will pose a
challenge if they're stored seperately, so unless there's a strong
driver for using the DB storage you might be better off trying to
model everything in the repository.

Re: JCR for everything (...or still some use of RDB)?

Posted by Alexandru Popescu <th...@gmail.com>.
On 10/28/06, Patrick Herber <pa...@ticino.com> wrote:
> Hello,
>
> I'm currently working at the design of a web collaboration application
> (things like knowledge-, time-, projects-, ... management) and I tought it
> would be very interesting to use jackrabbit for storing the content, since
> many features I need, like versioning, observation, access control, ...,
> come fast "out-of-the-box".
>
> Now, I'm new to Content Repositories and also to jackrabbit and I'm
> wondering: it's suggested to save everything in the content repository or,
> for some parts, of the application data is still prefered the use of a
> relational DB?
> I'm thinking, using the example of my project, about relationships between
> the different "content-objects", or about ratings and tags, which users can
> give to these objects.
>

Patrick, even if the details of your app are not so clear, I would say
that at first glance I would give a try to put everything in the JCR.
You can use relationships in the JCR (check mix:referenceable and the
REFERENCE type property. Also be aware of the multi-value properties).

./alex
--
.w( the_mindstorm )p.

> Thanks a lot for your suggestions.
>
> Best regards,
> Patrick
>
>