[Cosmo-dev] prototyping cosmo with jdbc instead of jcr

[Bobby Rullo]

Are you considering making "special" database structures for those  
sorts of datatypes that are not opaque to Cosmo? For example a  
CalendarCollection table with columns like "DisplayName" and  
"NodeID", an Events table with columns like "BeginDate", "EndDate",  
"CalendarCollectionId", etc.


>
> the advantages to such an architecture are many. with more control
> over how our data is stored, we can optimize for our most troublesome
> use cases (PROPFIND against a thousand event calendar, for example).
> by replacing the state-heavy but non-clusterable, mainly non-remotable
> jackrabbit with a more traditional j2ee style webapp talking to an
> rdbms, we achieve horizontal scalability with both server tiers. we
> can take advantage of mature, professional quality management tools
> for the app server and db server. and we don't have a "black box"
> component that few people understand, which reduces the number of head
> scratching bugs or performance problems that typically require a large
> dose of experience with the software to resolve.