[
https://issues.apache.org/jira/browse/OAK-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663024#comment-13663024
]
Jukka Zitting commented on OAK-834:
-----------------------------------
bq. I wonder how the deployment architecture that avoids this would look like?
In the JCR-3534 case separate repositories on distinct servers are accessing a
shared data store. Such a deployment architecture is necessary since Jackrabbit
doesn't support efficient remote access (i.e. the repositories need to be local
to each server) or scaling to lots of cluster nodes (i.e. repository replicas
are used instead of one big cluster). With Oak we should be able to put the
entire repository in the cloud where the DataStore in JCR-3534 is located.
Features like staged publishing which in JCR-3534 is achieved with a custom
content replication mechanism could be implemented by adding support for
workspaces and JCR features like {{Node.update()}}.
> Efficient copying of binaries across repositories with the same MK
> ------------------------------------------------------------------
>
> Key: OAK-834
> URL: https://issues.apache.org/jira/browse/OAK-834
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mk
> Reporter: Tommaso Teofili
>
> As a follow up on JCR-3534 discussions and implementation, we should also
> discuss how to handle a similar scenario in Oak.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
