There's a good reason for marketers to pay attention to Jackrabbit Oak, the newest version of the Apache Software Foundation's open source content repository — at least according to Chief Technical Officer and Hippo co-founder Arjé Cahn.
"Marketers should not have to choose between performance [in a website] and dynamic user experience," he told CMSWire
Hippo, which has offices in Boston, Mass. and Amsterdam, The Netherlands, offers an open source CMS. It's interested in Jackrabbit Oak because of its potential to help rapidly distribute dynamic content, and some members of the Hippo team have contributed code to the Jackrabbit project.
A content repository, according to the Apache Software Foundation, is "a hierarchical content store with support for structured and unstructured content, full text search, versioning, transactions, observation, and more."
Scalable and High-Performance
The first release version of Apache Jackrabbit Oak was launched in May and version 1.0.1 in late June. The Foundation characterizes it as "a scalable, high-performance hierarchical content repository designed for use as the foundation of modern world-class web sites and other demanding applications."
The previous version, called Apache Jackrabbit, was a content repository intended for the needs of conventional web sites and content management applications. The foundation notes that this original Jackrabbit, whose design decisions began almost a decade ago, was obsolete when it came to things like personalized/collaborative content and distributed/multi-platform solutions.
Oak is the name of a new architecture, supporting hierarchical content, distributed and loosely coupled CMSs, compliant with Java Content Repository (JCR) for environments using big data and user generated content, scalable and suitable for the cloud. JCR is an API (application programming interface) for accessing content repositories on a Java platform.
Hippo is interested in Jackrabbit Oak because, as Cahn told us, "we think its use of NoSQL data clusters might allow us to distribute personalized pages even more rapidly."
Real Life Example
He said that the "the conventional wisdom is that if you want to make a website really fast, flat – as opposed to personalized – pages are the way to go." As an example, he noted that CNN.com can quickly deliver pages worldwide because its content is distributed to servers around the world, and a user views CNN pages from a relatively nearby server.
But, Cahn pointed out, "this only works for HTML pages and doesn't take personalization into account."
Hippo provides global content distribution, but of raw content that is assembled by the CMS into a personalized version. Jackrabbit Oak might make their job easier, and might deliver their personalized pages faster.
That's why, he said, marketers and other website should not have to choose between a fast, globally-targeted website and one that dynamically delivers personalized pages.
- Microsoft Leaves Ballmer Bleeding as It Moves On
- Discussion Point: Why are We Still Stuck on Email?
- Sitecore Takes on the Competition with Version 8 #SYMNA
- A Look at the Top of Gartner's Mobile App Development World
- 6 Things to Consider Before Buying Enterprise Social Software
- Office 365 Now Makes You Look Smarter via Office Delve
- 5 Steps for Building a SharePoint Migration Plan