yes, this is a good point. have to think about it. on the first sight it feels a bit heavyweight for my usecase: in an osgi-microservice scenario without JCR/oak, and currently without sling engine but with some sling subprojects including launchpad i want to use sling distributed events and job processing and discovery. but the current implementations need to store some small parts of data in a shared repository, for which couchbase would suit well because it's used already by the microservices. but this is of course a very special usecase.
stefan >-----Original Message----- >From: Bertrand Delacretaz [mailto:[email protected]] >Sent: Tuesday, January 27, 2015 5:38 PM >To: dev >Subject: Re: [RT] Sling Resource Providers for NoSQL databases - MongoDB, >Couchbase > >Hi, > >On Tue, Jan 27, 2015 at 5:09 PM, Stefan Seifert <[email protected]> >wrote: >> ...we currently evaluate to integrate a Couchbase NoSQL database [1] into a >sling resource tree... > >As mentioned in a different thread about DynamoDB, it might be >interesting to consider writing a Couchbase backend for Oak instead. > >The advantages are inheriting Oak's indexing and other useful JCR >features, and maybe that helps with the other issues that you mention, >transient space etc. > >It's probably a bit more complicated, IIUC the current recommended way >is to implement an Oak DocumentStore, but that should be checked with >the Oak team. > >-Bertrand
