Competition between eXo, Liferay, and Jive is getting feisty. Liferay also released a new UI design framework this year in Liferay 6. eXo had this to say about their platform in comparison to Liferay's solution:
1) eXo is no longer an enterprise portal. Business needs have outgrown what a standalone portal framework can provide -- users want to integrate content, social features, collaboration capabilities.
2) eXo is a complete platform with all these services and eXo actually owns all its technologies, like our CMIS, JCR and KAX-RS implementations. Liferay is dependent on others for these critical pieces and it still has to win deals with content partners. eXo doesn't.
eXo Platform 3 has gotten either new support or API implementations for the following standards:
- CMIS (eXo's own implementation, xCMIS)
- Google's OpenSocial
- Social APIs for People and Activity Streams
The new platform architecture of eXo Platform 3.0 has been refactored for GateIn and has been modularized with extensions. This allows developers to modify GateIn features without changing the framework itself. This change also makes version migration much easier.
eXo Platform 3 has also done a lot with REST. Developers can create custom REST APIs on the fly and deploy them straight from the platform. eXo can also receive any third-party application data as portlets and interact with applications via web services. This lets you integrate third-party apps written in Java, .NET, PHP, or any other language via eXo Platform's native APIs.
For the shorter, 8-minute intro video, click here.