This has been a recurring question among customers when they are evaluating Liferay and we have been point by point explaining why Liferay DXP is such a better option compared to its community alternative. I recently wondered why this question keeps popping up in these meetings.
So I decided to do a quick search and found that there is no easy differentiation offered to end users. So here in this post I have outlined the definitive benefits on why you should prefer DXP over Liferay 7.
The difference is quite visible across the spectrum from the # of available portlets to the choice of tool for development.
Basic Difference between Liferay DXP and Liferay 7 (Community)
Other than the differences there are a lot of features that are pretty much exclusive to DXP and are non-existent in its community variant.
DXP Exclusive Features
Clustering in Liferay DXP is now redesigned and as like many of the out-of-the-box features. Clustering is re-implemented as an OSGi based module and it now gives support for clustering, non-open source app servers like:
- Oracle WebLogic
- IBM WebSphere
Audience Targeting 2.0
Liferay has introduces Audience Targeting with its DXP release that helps to segment your audience, target specific content to different user segments, and create campaigns to target content to user segments.
Support for Enterprise Databases
Liferay DXP gives out-of-the-box support for non-open source databases like:
- Oracle Database
- Microsoft SQL Server
- IBM DB2
- Sybase DBs
Elasticsearch has been replaced with the earlier search engine (lucene) in Liferay DXP. Elasticsearch is a highly scalable, full-text search and analytics engine that ship with Liferay Portal.