Liferay DXP Compatibility Matrix for Hosted Elasticsearch Services

Table of Contents

General Compatibility Note

The purpose of this article is to clarify the compatibility of Liferay DXP and the various hosted Elasticsearch options available on the market.

Liferay as an OEM partner of Elastic aims to provide compatibility with Elastic's own Elasticsearch releases and services. Liferay DXP is not compatible with any other Elasticsearch provider or service.

Compatibility Matrix

Service/Cloud Provider Name Liferay DXP 7.3 Liferay DXP 7.2 Liferay DXP 7.1 Liferay DXP 7.0
Elasticsearch Service on Elastic Cloud* Yes** Yes** (with Liferay restrictions) Yes** (with Liferay restrictions) Yes** (with Liferay restrictions)
Aiven for Elasticsearch No No No No
Amazon Elasticsearch Service No No No No
Bonsai Hosted Elasticsearch No No No No
Compose Elasticsearch Hosting No No No No
IBM Cloud Databases for Elasticsearch No No No No

 

* Also applies to Elastic Cloud subscriptions billed through the marketplace of the available cloud providers (Amazon Web Services (AWS), Google Cloud Platform (GCP), Microsoft Azure) as these Elastic Cloud deployments are managed through Elastic's cloud console.

** There are additional restrictions and known issues with Elastic Cloud to take into consideration when planning to host your Elastic Stack for Liferay DXP on Elastic Cloud. Please consult with the available user settings for the Elasticsearch Service and check Liferay DXP documentation to verify there are no conflicts between the Elasticsearch configuration or Elasticsearch-based features available in Elastic Cloud and those required by Liferay DXP. Some Liferay DXP use-cases may require configuration or features not available through Elastic Cloud.

Explanation

Why is Elastic Cloud the only service compatible with Liferay DXP?

  • Feature disparity: Amazon's Elasticsearch service is built on Amazon's Open Distro for Elasticsearch, a fork of the Open Source (OSS) version of Elastic's Elasticsearch which does not include Elastic's X-Pack modules (https://www.elastic.co/subscriptions). This means, security and other (commercial) Elasticsearch features that Liferay DXP integrates with (like Monitoring -> Kibana, or Cross-Cluster Replication) cannot be used with AWS's Elasticsearch service. In addition, Liferay DXP does not provide any vendor-specific integrations for security other than for Elastic's X-Pack Security. This feature incompatibility may also exist in other vendors' Elasticsearch services, therefore Liferay's connectors and features integrating with Elasticsearch are only tested with the binaries and services provided directly by Elastic.
  • Licensing restrictions: Elastic's X-Pack modules are subject to the Elastic License which prohibits cloud providers from building SaaS offerings using these products. Together with the feature disparity, this restriction significantly governs Liferay DXP's compatibility with Elasticsearch services.
  • Technical limitations:
    • Transport level connections are not supported in AWS and many other Elasticsearch services. This is required by Liferay DXP 7.2 and prior versions as they communicate with Elasticsearch over the Transport protocol only. Note: The Elasticsearch 7 connector that is bundled with Liferay DXP 7.3 by default uses the Java REST Client which communicates with Elasticsearch over HTTP.
    • JDK requirement for DXP 7.2 and prior versions: Elasticsearch and Liferay DXP must use the same Java version and distribution. This is because the Transport Client (used in these Liferay DXP version) relies on Java serialization. Note: The REST-client in Liferay DXP 7.3 uses HTTP. This communication protocol does not require Java serialization between DXP and Elasticsearch. Therefore, Liferay DXP 7.3 deployments are able run their Elasticsearch nodes on different JDKs.

Elastic, Elasticsearch, and X-Pack are trademarks of Elasticsearch BV, registered in the U.S. and in other countries.

Was this article helpful?
0 out of 0 found this helpful