AEM server holds both content and binary data. For a better deployment isolation and organizing data considering performance and scalability of AEM, the binary data(for eg media files) can be stored independently from the content nodes by configuring it.
Generally binary data is stored in a data store, whereas content nodes are stored in a node store. Both 'data stores' and 'node stores' can be configured by updating persistent identifier (PID) in OSGi configuration.
Say when we are working with large number of binaries, Adobe recommends to use an external data store instead of the default node stores. This provides better performance.
The external data store can be File Data Store, Amazon S3 Data Store, Azure Data Store which works well when we need to store binaries like media files.
Node store can be of two types 'Segment Node' Store & 'Document node' store. Segment node store is the basis of Adobe's TarMK implementation & document node store is the basis of AEM's MongoMK implementation in AEM6x.
Configuration PID's for each storage types are given below.
Document node store
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService.config
Segment Node Store
org.apache.jackrabbit.oak.segment.SegmentNodeStoreService.config
File Data Store
org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.config
Amazon S3 Data Store
org.apache.jackrabbit.oak.plugins.blob.datastore.S3DataStore.config PID
Azure Data Store
org.apache.jackrabbit.oak.plugins.blob.datastore.AzureDataStore.config
Summary: Thus by selecting the recommended configurations based on requirement, we can achieve a high performing AEM instance.
Note: The concepts are same for all AEM 6x versions, except a few minor configuration changes.
More Like This:
AEM 6.5 Site related new features
AEM 6.5 Specific new features in Assets section
New Features in AEM 6.5 Forms
Foundation updates in AEM 6.5 which a developer should be aware of
Cloud Manager for AEM 6.5 New features
Storage concepts in AEM 6.5
HTML Template language updates which needs to be observed with AEM 6.5
Generally binary data is stored in a data store, whereas content nodes are stored in a node store. Both 'data stores' and 'node stores' can be configured by updating persistent identifier (PID) in OSGi configuration.
Say when we are working with large number of binaries, Adobe recommends to use an external data store instead of the default node stores. This provides better performance.
The external data store can be File Data Store, Amazon S3 Data Store, Azure Data Store which works well when we need to store binaries like media files.
Node store can be of two types 'Segment Node' Store & 'Document node' store. Segment node store is the basis of Adobe's TarMK implementation & document node store is the basis of AEM's MongoMK implementation in AEM6x.
Configuration PID's for each storage types are given below.
Document node store
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService.config
Segment Node Store
org.apache.jackrabbit.oak.segment.SegmentNodeStoreService.config
File Data Store
org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.config
Amazon S3 Data Store
org.apache.jackrabbit.oak.plugins.blob.datastore.S3DataStore.config PID
Azure Data Store
org.apache.jackrabbit.oak.plugins.blob.datastore.AzureDataStore.config
Summary: Thus by selecting the recommended configurations based on requirement, we can achieve a high performing AEM instance.
Note: The concepts are same for all AEM 6x versions, except a few minor configuration changes.
More Like This:
AEM 6.5 Site related new features
AEM 6.5 Specific new features in Assets section
New Features in AEM 6.5 Forms
Foundation updates in AEM 6.5 which a developer should be aware of
Cloud Manager for AEM 6.5 New features
Storage concepts in AEM 6.5
HTML Template language updates which needs to be observed with AEM 6.5
No comments:
Post a Comment