I do agree. Partly because JSR 170 is marketed as 'JDBC for Content' :)
Perception of Jackrabbit is something that stores ""smartly"" & reliabily
content in database
Supports ''Content-oriented interface'' like EMB ( Enterprise Media Bean
JSR 086). JBoss does support EMB.
Simple Business Executive / Sponsor Brief for Content Projects :
"Architecturally Content Applications like CMS uses 'EMB' to save
content to 'ContentBase' using JCBC ( Java ContentBase Connectivity) i.e.
JCR"
" May use industry MPEG 21 framework for content interobility with our
partners"
Oracle Semantic Web, XML DB and Intermedia are great stuff but propriety tag
lingers and tough to get into mainstream applications :(
Q1) People would appreciate DBPersistenance subclass for Oracle which uses
the db features to the best. Has someone done similiar work ?
Q2) Also DBA does not appreciate the whole idea of all the content going in
just 1 big gigantic table. :(( How to get Content database refactored ?
Q3) Has someone try to model MPEG 21 Content Model on top of JackRabbit /
170 model. BRICK ( www.brickcommunity.org ) does something like that. All of
sudden JCR 170 become mainstream media technology :)
Chand
----- Original Message -----
From: "Miro Walker" <[EMAIL PROTECTED]>
To: <jackrabbit-dev@incubator.apache.org>
Sent: Friday, February 03, 2006 2:42 AM
Subject: RE: DP Persistence manager implementation
I really like the idea of jackrabbit / JCR becoming an RDBMS-grade
repository, but it's a long way from there now and in fact a key
motivation of companies I've spoken to about using JCR has been around
their need to get away from using filesystems to store data. Many
organisations see RDBMS support as a key feature of jackrabbit et al.,
and JCR as a mechanism to allow them to make best use of their existing
investment in Oracle, MS SQL Server, etc. while still providing a
content-oriented interface. So, jackrabbit starts to find a place as a
webdav to RDBMS interface layer, for example.
Miro
-----Original Message-----
From: Serge Huber [mailto:[EMAIL PROTECTED]
Sent: 03 February 2006 10:35
To: jackrabbit-dev@incubator.apache.org
Subject: Re: DP Persistence manager implementation
Just on a quick note, from what I understand of Jackrabbit's main
design, is that it is optimized for usage scenarios where you :
read-a-lot, write-a-little
Or rather that your read to write ratio is large. In your scenario it
seems that you are writing quite often or is this a misconception ?
Apart from that, I do agree that adding too much logic to a "Simple" DB
PM would not be a good idea. We could indeed add more DB PMs, possibly
without copy-pasting DB code. A modification to allow for JNDI lookup
though would not be significant.
As for thread-writing and such, you have to be careful with transaction
semantics, which *must* be preserved. I think one interesting thing to
look into might be optimistic locking, where all the locking and object
changes checks are made at the end of a transaction, with the
possibility of the transaction to be rejected, but of course this
depends on the usage scenario and whether this is acceptable or not.
Regards,
Serge Huber.
Przemyslaw Pakulski wrote:
Marcel Reutegger <[EMAIL PROTECTED]> wrote:
this is not quite true. the actual store operation on the persistence
manager is synchronized. however most of the write calls from
different threads to the JCR api in jackrabbit will not block each
other because those changes are made in a private transient scope.
only the final save or commit of the transaction is serialized.
that's only one part of the whole write process
But in fact in real application most of business method ends with
either save, checkin or commit, and in consequence concurrent calls of
this methods will block each other and wait for storing modified data.
We are using versioning feature intensively, and we have performance
problems mainly with write operations. Additionally we notice big
performance degradation when we switch to SimpleDBPersistenceManager
with MySQL or other db using network communications. So it looks like
overall performance depends much on PM implementation because all
save/checkin operations wait for PM until he finish all his work.
One solution to avoid blocking write operations could be special
thread/s responsible for flushing data to PM, but i don't think so
that Jackrabbit uses asynchronous processing.
even if such a persistence manager allows concurrent writes, it is
still the responsibility of the caller to ensure consistency. in our
case that's the SharedItemStateManager. And that's the place where
transactions are currently serialized, but only on commit.
If concurrent write performance should become a real issue that's
where we first have to deal with it.
If there exists any singleton component on top of PM, which is
reponsible for serializing all saves, checkins or transactions then
naturally using connection pools doesn't help, but maybe it means that
Jackrabbit is not designed to work effectively in multithreaded
environment.
Even if usage of connection pool is not reasonable in current design,
I think it is worth to consider JDBC batch updates instead of single
updates to gain better DBPM performance.
Regards
Przemo Pakulski
www.cognifide.com
