Adobe Experience Manager helps you organize and manage the delivery of creative assets and other content across all of your digital marketing channels. Experience Manager customers who take advantage of MongoDB can deploy a highly scalable content repository to support their business needs, as well as migrate content from legacy systems. In this session, you'll learn how you can use MongoDB to deploy AEM systems at scale. The session will cover installation, sizing, and the tools available to automate and manage your cluster.

2. Adobe Experience Manager
Clustering Made Easy on MongoDB

3. Agenda
Introduction to AEM and MongoDB
JCR2 – JackRabbit OAK
MongoMK Internals
MongoDB + AEM
High Availability
Scalability

4. No interactive QA today!
I'll be answering some of your questions at the end

6. What is Adobe Experience Manager?
"It’s a comprehensive content management solution for building
websites, mobile apps and forms. And it makes it easy to
manage your marketing content and assets."

7. Adobe Experience Manager
• Web Content Management
• Digital Asset Management
– Multi-site and Channels
– Brand Consistency
– Governance
– Multi-version
– Cross Platform
• Communities, Social, Personalization …

8. MONGODB FEATURES
JSON Document Model
with Dynamic Schemas
Auto-Sharding for
Horizontal Scalability
Text Search
Aggregation Framework
and MapReduce
Full, Flexible Index Support
and Rich Queries
Built-In Replication
for High Availability
Advanced Security
Large Media Storage
with GridFS

9. MongoDB
GENERAL PURPOSE DOCUMENT DATABASE MULTI PLATFORM

10. Why is MongoDB ideal for AEM?
General Purpose Database
Multiplatform
Scalable
Flexible Data Model
High Availability out-of-the-box

11. Why is MongoDB ideal for AEM?
Suitable for Content Management Systems
Runs practically everywhere
You are not constrained by your data set
Fits perfectly AEM flexibility needs
Reduces operational overhead

12. AEM + MongoDB => Business Value
• Improved Operational Efficiency
• Team Collaboration w/ Projects & Workflows
• Performance at Scale
• Enables Social and Community features
• Clustering

13. AEM is a Certified MongoDB
Enterprise Solution

14. AEM Internals

15. AEM Environments
AEM Node
AUTHOR ENVIRONMENT
PRODUCTIONBACK-OFFICE
Storage Layer AEM Node
AEM Node
AEM Node
AEM Node
PUBLISH ENVIRONMENT
Storage
LayerWORKFLOW

16. AEM Architecture
• Main Components
– Apache Felix
– Sling
– Jackrabbit
• OSGi container for web framework and Java Content Repository -
JCR

17. AEM Internals
“Jackrabbit Oak is an
effort to implement a
scalable and
performant
hierarchical content
repository…”
AEM6
JACKRABBIT OAK CONTENT REPOSITORY

18. JCR 2 – Jackrabbit Oak

19. Jackrabbit Oak
• Open Source Apache Project
• Fully JCR2 (JSR -283) Complaint
• https://jackrabbit.apache.org/oak/docs/index.html
"Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository for use as the foundation of modern
world-class web sites and other demanding content applications."

20. JCR2
• Content Repository API for JAVA (JCR)
– Version 1(JCR1 – JSR 170)
• https://www.jcp.org/en/jsr/detail?id=170
– Version 2 (JCR 2 – JSR 283)
• https://jcp.org/en/jsr/detail?id=283

21. Jackrabbit Oak – JCR 2
Repository has it’s
own Query Engine
which includes
“pluggable” indexing,
concurrency and
version control:
Query Languages:
- Xpath
- SQL-2

22. Jackrabbit Oak – JCR 2
Repository can also
be configured to use
different storage
layers:
Storage Options:
- TAR
- MongoDB
- RDBMS

23. Jackrabbit Oak – JCR 2
Hierarchical – Structured and binary data
Query – SQL, Xpath and Java language binding
Access Control on Node and Property level
Versioning – Modeled after WebDAV DeltaV (RFC 3253)
Locking – Shallow and deep
Asynchronous Observation

24. MongoMK

25. MongoDB MicroKernel
• AEM 6 Scalable Storage Solution
• Flexible
• Multi-Datacenter Deployments
• Geo Distributed Content
• Auto-Failover

26. MongoMK - Content
Metadata
Binary / Blobs

27. MongoMK
• Collections
– *Nodes: Nodes and properties
• Metadata information
– *Blobs: Stores binary data
• Binary file chunks
– ClusterNodes: Cluster configuration data
– Settings: general application configuration data
– Changes: revision tracking
*sharding collections

28. Binary / Blobs
MongoMK – Metadata
Metadata

29. MongoMK – Content
Content is
model as tree of
properties.
{
"_id": "2:/oak:index/damLastModified",
"_lastRev": {
"r0-0-1": "r149058c86b0-0-1",
"r0-0-2": "r148f6133166-0-2"
},
"direction": {
"r148f5d8843e-0-1": ""descending""
},
"_modified": NumberLong("1413137335"),
"async": {
"r148f5d8843e-0-1": ""async""
},
"jcr:primaryType": {
"r148f5d8843e-0-1": ""nam:oak:QueryIndexDefinition""
},
"propertyNames": {
"r148f5d8843e-0-1": "["nam:jcr:lastModified"]"
},
"type": {
"r148f5d8843e-0-1": ""ordered""
},
"_deleted": {
"r148f5d8843e-0-1": "false"
},
"_commitRoot": {
"r148f5d8843e-0-1": "0",
"r148f5d8bed2-0-1": "0"
},
"reindex": {
"r148f5d8843e-0-1": "true",
"r148f5d8bed2-0-1": "false"
},
"_modCount": NumberLong("5"),
"_children": true

30. MongoMK – Data Model

31. MongoMK – Data Model
• Documents represent attributes or portions of the data
– This data keeps track of all changes occurred over time on an
attribute
– Multi-versioning support
• _id represents the node attribute according with a hierarchical / tree
structure
• _deleted field keeps track of deleted and created timestamps
• _revisions is used for concurrency and transaction control
– All changes are based on a revision
– Once revisions are committed that will be pointing to value "c"
– A revision is formed by
• Timestamp
• Counter
• ClusterId

32. MongoMK – Version Control
Revisions of content are maintained as
separate trees

33. MongoMK – Data Model

34. MongoMK – Versioning & Concurrency
System provides version and concurrency
control of content revisions.

35. MongoMK - Versioning & Concurrency
• Transactions are handled by keeping reviews on a commit Root document
– commitRoot is the upper level document in the hierarchy where a transaction
initiated
• There's a conditional update to manage the collisions
{_id : “1:/home”, “_collisions.r14979e4b424-0-1” : { $exists :
false }}

36. MongoMK – Versioning & Concurrency

37. Binary / Blobs
MongoMK – Binary Data
Metadata

38. AEM Blob Storage
TAR MONGODB S3

39. MongoMK - Blobs
• Binary data can be stored either sharing the same Node
Data Storage Engine or a specific one
– Using the same simplifies the operational complexity
• This mechanism ensures:
– De-duplication of chunks
– Chunks immutability

40. MongoMK - Blobs

41. MongoMK - Blobs

42. Scale

43. Why is MongoDB ideal for AEM?
General Purpose Database
Scalable
Flexible Data Model
High Availability out-of-the-box

44. AEM - MongoMK
• Clustering: What’s the impact on the business if AEM is down?
– Productivity: Do you have a large number of content
contributors and developers that will be effected?
– Content Freshness: Are you in a business where high content
freshness, and time sensitive content updates are imperative?
• Scale: Is the Authoring UX suffering at scale?
– Large Volumes of content? Need capacity beyond a single
server.

45. AEM “Clustering”
AEM
Primary Secondary Secondary
AEM
Secondary
AEM
Arbiter
AEM
AWS-
CENTRALDC-WEST DC-EAST

46. AEM “Clustering”
AEM
Primary Secondary Secondary
---
Secondary
AEM
Arbiter
AEM
AWS-
CENTRALDC-WEST DC-EAST

47. AEM “Clustering”
AEM
--- Primary Secondary
---
Secondary
AEM
Arbiter
AEM
AWS-
CENTRALDC-WEST DC-EAST

48. AEM “Clustering”
---
--- --- Primary
---
Secondary
AEM
Arbiter
AEM
AWS-
CENTRALDC-WEST DC-EAST

49. AEM – Geographical Distribution Needs

50. AEM Sharded Cluster
AEM AEM AEM
DATA PARTITIONED ACROSS SERVERS FOR UNBOUNDED HORIZONTAL SCALABILITY
ELIMINATE
EXCESSIVE
REDUNDANCY

51. AEM – Large Enterprise Solution

52. Social

53. MongoMK Supports UGC
AEM AEM AEM
SCALES ON
READ AND
WRITES
(FOR UGC)

54. MongoMK - UGC
• Social: Are you looking to implement Community features in
AEM?
• Scale: Does the customer need to scale to support large
volumes of content and page views?
• Scale: What is the UX (performance) of your web and mobile
channel as content and visitors grow?
• Scale: Is there an opportunity to lower infrastructure cost?

55. et summa

56. AEM + MongoDB
• AEM is a certified MongoDB Enterprise Solution
• MongoDB and AEM have a very good fit
• MongoDB is AEM solution for scalability demands/needs
• Highly Available storage layer
• Scalable
• User Generated Content ready
– Reads & Writes

57. How do Decide ?

58. Where to get more information?
• Online Documentation
– http://docs.adobe.com/docs/en/aem/6-0.html
– http://www.mongodb.com/lp/contact/mongodb
-adobe-experience-manager
• Technical Presentations
– http://www.mongodb.com/presentations/apac
he-jackrabbit-oak-mongodb
• White Papers
– http://www.mongodb.com/white-papers

59. Register now: mongodbworld.com
Super Early Bird Ends April 3!
Use Code NorbertoLeite for additional 25% Off
*Come as a group of 3 or more – Save another 25%

60. MongoDB World
Joint Session from Adobe & MongoDB on AEM
Deployment and Operational practices

61. Feel free to reach out!
http://www.mongodb.com/norberto
norberto@mongodb.com
@nleite

62. For More Information
Resource Location
Case Studies mongodb.com/customers
Presentations mongodb.com/presentations
Free Online Training education.mongodb.com
Webinars and Events mongodb.com/events
Documentation docs.mongodb.org
MongoDB Downloads mongodb.com/download
Additional Info info@mongodb.com

63. http://cl.jroo.me/z3/v/D/C/e/a.baa-Too-many-bicycles-on-the-van.jpg
Questions?
@nleite
norberto@mongodb.com
http://www.mongodb.com/norberto