wu-sheng opened a new issue #6219: URL: https://github.com/apache/skywalking/issues/6219
Hi Community, Elastic announced they are changing the license of ElasticSearch server recently, from Apache 2.0 to SSPL. Official announcement is here, https://www.elastic.co/pricing/faq/licensing SSPL has been confirmed as a Catalog X LICENSE. So we can't only focus on it anymore. We need to consider other storage options. Right now, we still have InfluxDB, TiDB, H2 server still in Apache 2.0 licensed. As one optional plugin, we need to focus on the client driver license. Right now, we are only using ElasticSearch 7.5.0 and 6.3.2 drivers, which are both Apache 2.0 licensed. So, we are safe. For further upgrade, here is their announcement. ``` Many of our products and projects continue to be under Apache 2.0, including our client libraries ``` ``` > I'm using Elasticsearch via APIs, how does this change affect me? This change does not affect how you use client libraries to access Elasticsearch. Our client libraries remain licensed under Apache 2.0, with the exception of our Java High Level Rest Client (Java HLRC). The Java HLRC has dependencies on the core of Elasticsearch, and as a result this client library will be licensed under the Elastic License. Over time, we will eliminate this dependency and move the Java HLRC to be licensed under Apache 2.0. Until that time, for the avoidance of doubt, we do not consider using the Java HLRC as a client library in development of an application or library used to access Elasticsearch to constitute a derivative work under the Elastic License, and this will not have any impact on how you license the source code of your application using this client library or how you distribute it. ``` **The only impact to us is**, if we move on to support the 8.x or upgrade the driver to 7.11+(include 7.11), we have to wait for their latest Apache 2.0 licensed driver. ___ Besides the potential risk of ElasticSearch's company behaviors, we need to consider other more general available database solution. There are several in my mind. 1. Apache Cassandra, https://cassandra.apache.org/. cc @michaelsembwever 2. Apache Solr, https://lucene.apache.org/solr/. Sub-project of Lucene, which is the core of ElasticSearch too. cc @dmsolr 3. Apache IoTDB, https://iotdb.apache.org/. cc @jixuan1989 4. Hybrid, M3 https://m3db.io/, focuses on metrics, Cassandra or something focuses on the trace/log. Besides above, I was having long discussion with @hanahmily, we should have plan to build SkyWalking own storage solution, focusing on metrics/log/trace observability area data, without bothering about the transaction and consistency of most database provided. We should be able to delivery a higher performance, lower resource cost hybrid database solution as a new sub project under SkyWalking's umbrella. To all @apache/skywalking-committers, what do you prefer? And what do you want to add about this event? It is welcome to join this thread. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
