Adobe Experience Manager (AEM) as a Cloud Service
Architecture
Multi-tenant SaaS on Adobe Managed Services (AWS/Azure). Three-tier topology: Author (single-tenant, ~200GB Oak segment tar), Publish (auto-scaled farm, Oak composite blob store → S3/Blob Storage), Preview (ephemeral). Dispatcher (Apache + mod_dispatcher) at edge — cache invalidation via Sling Resource Invalidation (SRI) with ~100ms global propagation.
Content Model & APIs
- Content Fragments: Structured, channel-agnostic content with variation support. GraphQL schema auto-generated from CF models.
- Experience Fragments: Reusable page regions (header, footer, promo) — not headless-friendly.
- Assets: Native DAM (AEM Assets) with Smart Tags (Adobe Sensei), dynamic media (Scene7), rendition workflows.
- GraphQL: Persisted queries only (no ad-hoc in production). Endpoint:
/graphql/execute.json. Supports fragments, unions, interfaces.
Hidden Costs & Gotchas
- Dispatcher config management: Git-based, but
dispatcher-sdkvalidation runs in Cloud Manager pipeline — 30-45 min per deploy. - Content migration: No native bulk import API for Content Fragments. Use
aem-content-package-maven-pluginor RTE-based scripts. - Search: Oak Lucene indexes — custom indexes require Adobe Support ticket for production deployment.
- Forms: AEM Forms = separate license ($100K+/yr). Not included in Sites license.
When to Choose
You're all-in on Adobe: Analytics, Target, Campaign, Creative Cloud. You need asset-centric workflows (creative → DAM → Sites → Target). Budget >$500K/yr. Team has/scan hire AEM specialists (rare, expensive).