Multi-tenancy 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 :

• Managing dependencies
• Preventing code duplication
• Managing deployment scope
• Overlays
• Workflow launchers
• Vanity URLs
• Component Groups
• Testing

Operational Considerations:

• Shared Resource.
• Performance
• Logging'
• Backup and restore
• Security consideration
• 
  
• ACL
• Administartive Sessions
• Full text indexing
• User authentication
• Servlets
• Governance
• 
  
• Stakeholder Alignment
• Release Cycles
• Support
• Encouraging Reuse
• 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