not sure if this is of any help for your usecase - but do you need the full JCR features and complexity underneath sling, or only a sling cluster + storage in mongodb?
if you need only basic resource read and write features via the Sling API you might bypass JCR completely and directly use a NoSQL resource provider for MongoDB, see [1] and [2]. but please be aware that: 1. the code might not be production-ready for heavy usages yet (not sure how much it is used) 2. it does not add any support for cluster synchronization etc. if your multiple nodes write to the same path you have to take care of concurrency yourself 3. the code is not yet migrated to the latest resourceprovider SPI from sling 9-SNAPSHOT, but should still run with it 4. it has not built-in support for ACLs etc., you have to take care of this yourself this resource provider is only a thin layer above the MongoDB java client, so it should be possible to have full control what mongodb features are used in which way. stefan [1] http://sling.apache.org/documentation/bundles/nosql-resource-providers.html [2] https://github.com/apache/sling/tree/trunk/contrib/nosql
