Exploring the Sling Feature Model: Part 2 - Composite NodeStore

Published on by Dan KlcoPicture of Me Dan Klco

In my previous post Exploring the Sling Feature Model, I described the process of migrating from a Sling Provisioning project setup to a Sling Feature Model project. Now that we have the Sling Provisioning Model project converted, we can move on to the fun stuff and create a Composite NodeStore. We'll use Docker to build the Composite Node Store in the container image. Creating the Composite NodeStore Seed The Composite NodeStore works by combining one or more static "secondary" node stores with a mutable primary NodeStore. In the case of AEM as a Cloud Service, the /apps and /libs directories are mounted as a secondary SegmentStore, while the remainder of the repository is mounted as a MongoDB-backed Document Store.