Hi, Re 2: performance of any system is really quite dependent on the workload. I would advise not too take anyone’s word, but run tests that reflect your intended usage. The Oak project has a good set of performance tests that can get you started (sorry - currently offline, but IIRC it’s the “benchmark” package in oak-run. If your final deployment scenario includes Sling you might just run an http performance tool against Sling.
Michael On 18/05/17 16:37, "Chetan Mehrotra" <[email protected]> wrote: >Answers to few of the queries inline > >> 1. Can we access a single Oak repository from multiple nodes over >> network? I believe so, but please confirm as the docs don't seem to make >> this very clear. > >Yes just spin multiple Oak instances connected to same DB or Mongo > >> 3. Can we have synced copies/repository? > >Generally you would use sidegrade support for that [1] but thats not >incremental so would do a complete diff for each run. There are plans >to add secondary node store support to sidegrade which would allow >incremental update of secondary store using oak-upgrade tooling. > >> 3.a Can Secondary Node run disconnected? > >Yes its a normal SegmentNodeStore (with some added meta props). So can >be used in disconnected mode > >> 3.b Can Secondary node work with RDBDocumentStore ? > >Yes > >> 3.c. In case we can sync the repository and some content is versionable, >> can we select what version to use? I imagine we can with Secondary Node >> solution. > >For that you need to rely on JCR API. At Secondary Node level its all content > >Chetan Mehrotra >[1] https://jackrabbit.apache.org/oak/docs/migration.html#Sidegrade
