12
#evolverocks Understanding a typical AEM deployment ABHISHEK DWEVEDI August 31 st , 2016

EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

Embed Size (px)

Citation preview

Page 1: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

#evolverocks

Understanding a typical AEM deployment ABHISHEK DWEVEDI

August 31st, 2016

Page 2: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

2#evolverocks

Understanding a typica l AEM deployment

1. Oak Architectures2. Typical AEM Environment3. Dispatcher Module Deployment 4. AEM Communities

Page 3: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

3#evolverocks

Oak Architectures: Single TarMK instance

A single TarMK instance runs on a single server. Default setup for Author instances Advantages:

Simplicity Easy maintenance Good performance 

Disadvantages: Not scalable beyond the limits of the server capacity No failover capacity

Page 4: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

4#evolverocks

Oak Architectures: TarMK Cold Standby

One TarMK instance acts as the primary instance. The repository from the primary is replicated to a standby failover system. The failover server is running in cold-standby mode, which means that the

HttpReceiver of the instance is running. Advantages:

Simplicity Easy maintenance Good performance Failover is provided 

Disadvantages: Not scalable beyond limits of the server capacity One server is idle

Page 5: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

5#evolverocks

Oak Architectures: TarMK Farm Multiple Oak instances run with one TarMK instance each. The TarMK repositories are independent and need to be kept in sync. This is the default deployment for AEM Publish instances. Advantages:

Good performance Scalability for read access is provided Failover is provided 

Disadvantages: Write access kept in sync between instances

Page 6: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

#evolverocks

TYPICAL AEM ENVIRONMENT

Page 7: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

#evolverocks

DISPATCHER MODULE DEPLOYMENT

webserver

Dispatcher

docroot

webserver

Dispatcher

docroot

webserver

Dispatcher

docroot

webserver

Dispatcher

docroot

AEM

Publish

AEM

AEMrender the page

write it into the docroot

home.html

Page 8: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

8#evolverocks

AEM COMMUNIT IES : IMPLEMENTING THE COMMON STORE• Social Resource Provider (SRP)• An API that abstracts the

storage• Implemented three different

ways• MongoMK JCR SRP (JSRP)• Adobe SRP (ASRP)• Mongo SRP (MSRP)

Page 9: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

9#evolverocks

J S R P : J C R S O C I A L R E S O U RC E P R OV I D E R

9

9AEM Author

• Publish instances are clustered with MongoMK

• Default storage mechanism• Easy to setup UGC• UGC is only available on publish

instances• Publish Farm is not utilized

MongoMK

AEM Publish

3

AEM Publish

2

AEM Publish

1

Page 10: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

#evolverocks

ASRP: Adobe Social Resource Provider

TAR TAR TAR

AEM Publish Farm

Adobe Social Cloud

AEM Author

• Recommended for managed UGC

• No setup needed• Integrates with Adobe Social

Analytics Pipeline and Moderation

• Fast

Page 11: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

#evolverocks

M S R P : M O N G O S O C I A L R E S O U RC E P R OV I D E R

TAR TAR TAR

AEM Author

AEM Publish Farm

• Recommended for on premise UGC

• Required to setup a mongo replica set and solr cloud

• Fast and scaleable

Page 12: EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment

#evolverocks

THANK YOU!