Multitenancy and Concurrent Development in AEM

Solution :


Benefits and Challenges to implement a multi-tenant environment. Challenges include: 

•  Additional technical complexity 
•  Increased development overhead 
•  Cross-organization dependencies on shared resources 
•  Increased operational complexity 

Despite the challenges faced, running a multitenant application does have benefits, such as: 

• Reduced hardware costs
• Reduced time to market for future sites 
• Lower implementation costs for future tenants
• Standard architecture and development practices across the business 
• A common codebase

 Development Techniques :

1. Managing dependencies
2. Preventing code duplication
3. Managing deployment scope
4. Overlays
5. Workflow launchers
6. Vanity URLs
7. Component Groups
8. Testing

Operational Considerations:

1. Shared Resource.
2. Performance
3. Logging'
4. Backup and restore

Security consideration

1. ACL
2. Administartive Sessions
3. Full text indexing
4. User authentication
5. Servlets

Governance 

1. Stakeholder Alignment
2. Release Cycles
3. Support
4. Encouraging Reuse
5. Improving Visibility  

Checklist Use the following checklist to ensure that you have considered the important pieces of a multitenant AEM deployment: 

 A strong architecture/central team in place 

 High-level executive buy-in 

 Business unit level buy-in 

 Governance and processes are in place 

 An emphasis on testing 

 Agreement on release/upgrades and schedules 

 Common infrastructure and operations (storage, backup/restore) 

 Single place (e.g. wiki) to document the platform and each individual application 

 Common development and deployment strategy 

 Development of a core platform of services used by all sites 

 Extensive product knowledge by development and operation teams

Reference :

https://solutionpartners.adobe.com/content/dam/spp_assets/public/public_4/Multitenancy_and_Concurrent_Development_in_AEM.pdf