Exploring the Sling Feature Model: Part 2 - Composite NodeStore | AEM Community Blog Seeding | Community
Skip to main content
kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
August 4, 2020

Exploring the Sling Feature Model: Part 2 - Composite NodeStore | AEM Community Blog Seeding

  • August 4, 2020
  • 1 reply
  • 960 views

BlogImage.jpg

Exploring the Sling Feature Model: Part 2 - Composite NodeStore by Perficient

Abstract

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.

Read Full Blog

Exploring the Sling Feature Model: Part 2 - Composite NodeStore

Q&A

Please use this thread to ask the related questions.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

J
jeremylanssiers
Level 3
August 8, 2024

Is there any official documentation supporting this statement? 

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.

 

Terms & ConditionsAccessibility statement

Loading footer...