![]() ![]() ![]() However, Solr still thrives as a project on its own and matches Elasticsearch on many fronts. Elasticsearch was created in 2010 to fill in the gaps left by Solr when it comes to search. Solr was created in 2008 as a solution for data search. Given the importance of Elasticsearch, the CNCF seems like a natural home for the project. With this new fork, AWS and other organizations have the opportunity to define a new direction for the product, one that isn’t controlled by a single organization.įor this to happen, though, the AWS fork will need to be governed by a vendor-neutral oversight committee, something like the CNCF (Cloud-Native Computing Foundation). As a result, suggestions from outside contributors were routinely rejected. One complaint that companies like AWS have had is that Elastic has taken the focus off the open-source project and only invested in their proprietary solutions. It would include all the functionality of Elasticsearch and has the potential to grow to be more powerful than the old Elasticsearch in the future. It would be based on the last Apache-licensed Elasticsearch version 7.10. This fork has drawn support from others in the logging space like Logz.io and is likely to be the successor to the old open-source Elasticsearch. They have invited other organizations to join with them in making this fork the truly open-source Elasticsearch that everyone needs. That was about to change with the Elasticsearch licensing change.ĪWS has now announced that they will be forking Elasticsearch under the Apache 2.0 license. A fork is a separate version of the code and would have its own maintainers and open-source community developing it separately. The original would still be the version that the open-source community contributes to. However, a distro is a mere copy of the original with some modifications. They likely anticipated the license change and wanted to secure their Elasticsearch cloud service from the company Elastic. The AWS fork of ElasticsearchĪWS announced the Open Distro for Elasticsearch back in 2019. That’s what we discuss in this article - the best alternatives for Elasticsearch after the license change. However, one look at the license by your legal team may show that the SSPL license is a risk your company will not want to take. Elastic says that the SSPL license will not affect most users. For Elasticsearch users, the question is whether to continue using Elasticsearch under the SSPL license or to look for an alternative. ![]() Since then, a flurry of activity has been underway from every side. It’s over a month since Elastic (the company) announced that they are changing the open-source licensing for Elasticsearch from Apache 2.0 to SSPL. ![]()
0 Comments
Leave a Reply. |