You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/04/22 11:21:16 UTC

[jira] [Created] (OAK-788) File backend for the SegmentMK

Jukka Zitting created OAK-788:
---------------------------------

             Summary: File backend for the SegmentMK
                 Key: OAK-788
                 URL: https://issues.apache.org/jira/browse/OAK-788
             Project: Jackrabbit Oak
          Issue Type: Sub-task
          Components: core
            Reporter: Jukka Zitting
            Assignee: Jukka Zitting


The SegmentMK now has two backends: one in-memory and the other based on MongoDB. Since MongoDB isn't readily available everywhere and the in-memory backend obviously isn't suited for production use, it would be useful to have an additional SegmentMK backend based on just the local file system.

Inspired by, though not directly based on, the proprietary TarPM in CRX, I propose to implement such a backend using the tar file format as the basis.

Unlike the MongoDB backend or the original TarPM, such a "TarMK" backend would be designed primarily for optimum performance on a *single-node* deployment, i.e. without support for clustering. A typical deployment could be replicated set of independent copies of a repository, designed for massively parallel read-only or mostly-read workloads.

--
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