For term of flexibility here, I meant the ways we can query the model and I think in relational model it is very flexible, but in nosql it is by the keys you define.(By the way I don't have much knowledge on nosqls)
Unfortunately I can't find much documentations around Jackrabbit. In compare with other Apache projects it has poor documentation. I don't know how developers have developed nosql model in Jackrabbit. and how it fetches data. When for example it is lazy and when not... On Sun, Mar 6, 2011 at 7:24 PM, Alexander Klimetschek <aklim...@adobe.com>wrote: > On 06.03.11 14:57, "Reza Aliakbari" <raliakb...@gmail.com> wrote: > > >I think nosql has good performance but less flexibility. > > Oh, no! First of all, there is no general "nosql" feature set. There are > many nosql storages that totally focus on performance, but don't give lots > of features or schema/content structure abilities, these end up as simple > key-value stores. > > But there are also others that really focus on giving you a better data > model than relational databases, while not so much focussing on special > in-memory performance etc. (having performance generally at the same level > as your typical RDBMS, however that also depends on the application and > how it uses the data storage, etc. pp.). > > Especially JCR is at its heart about a more natural modeling and > unstructured data. Hence you get much more flexibility than with SQL > databases! RDBMS require you to change your schema every time you want to > add a new field, this is a big inflexibility. > > Regards, > Alex > > -- > Alexander Klimetschek > Developer // Adobe (Day) // Berlin - Basel > > > > >
