Re: [dna-dev] Several interesting InfoQ articles about JCR

You're right that JCR handles heterogeneous data better than almost anything else, especially when the information structure changes/ evolves over time. And I thought the InfoQ architecture was brilliant - use multiple independent JCRs for infrequently changing data, eliminating the need to create/maintain/scale a cluster. Very elegant and simple solution. And in this particular case, it doesn't really matter if there is a slight difference in content among the different machines during the push of new information to the independent repositories. But can you elaborate on your thought that JCR might not be useful for transactional data? IMO, JCR is useful in a lot of situations, and of course it is limited in others. Right now, the implementations don't do clustering or very large repositories well. Most impls also seem to be limited in the efficient handling of large numbers of children for any given node. Incorporation of information outside of JCR is also difficult, as it has to be done above JCR - although DNA will change this. But I'm not sure that frequently changing data is universally a limitation. Perhaps frequent additions of large volumes of data are a problem because you quickly get to volumes of data that are too large. Or frequent changes to data may be a problem if versioning is used, as it could quickly lead to unusable numbers of versions. On Jun 10, 2008, at 9:45 PM, Michael Neale wrote: