AEM content repository is based on Apache OAK, which implements the JCR standard. OAK allows to plug different indexers into the repository. An indexer is a mechanism to optimize the searches on specific paths/node types/properties through the use of…
Hotel Silken, Madrid, 8 June 2017: the first AEM conference in Spain, organised by Adobe, Translations.com, CodeBay/CodeLand and AKQA. In a very appealing location, CodeBay and CodeLand had the pleasure to actively participate in the organisation, proposing two different…
In this post we are going to analyze some of the common recommended AEM deploy models, making a comparison between them and trying to identify the appropriate solution based on some KPIs. Note that we are not mentioning all different deploy…
With the introduction of AEM 6 and its following releases, creation of clusters of author instances has been rethought. The typical persistance model which supports clustering in AEM uses MongoDB.Adobe suggests to define a cluster of author AEM instances…
The AEM platform starting from AEM 6 is based on a Jackrabbit OAK repository (replacing the Jackrabbit 2.X repository of previous versions). This repository can be split in two different storage elements: the Node Store and the Data Store (also…
Sometimes, when you are involved in AEM projects, it could come up a requirement that you will need to load some content from an external resource provided by the client in a component to be rendered in pages using…
