Elasticsearch Alternatives
-
cockroach
CockroachDB - the open source, cloud-native distributed SQL database.
-
opendistro-build
🧰 Open Distro for Elasticsearch Build Scripts
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
react-native
A framework for building native apps with React.
-
Ansible
Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
-
moment
Parse, validate, manipulate, and display dates in javascript.
-
Scrapy
Scrapy, a fast high-level web crawling & scraping framework for Python.
-
Babel (Formerly 6to5)
🐠 Babel is a compiler for writing next generation JavaScript.
-
jest
Delightful JavaScript Testing.
-
Pandas
Flexible and powerful data analysis / manipulation library for Python, providing labeled data structures similar to R data.frame objects, statistical functions, and much more
-
Symfony
The Symfony PHP framework
-
NumPy
The fundamental package for scientific computing with Python.
-
matplotlib
matplotlib: plotting with Python
-
SaltStack
Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
-
Sinatra
Classy web-development dressed in a DSL (official / canonical repo)
-
faker
A library for generating fake data such as names, addresses, and phone numbers.
-
bleve
A modern text indexing library for go
-
pytest
The pytest framework makes it easy to write small tests, yet scales to support complex functional testing
-
phpMyAdmin
A web interface for MySQL and MariaDB
-
JRuby
JRuby, an implementation of Ruby on the JVM
Posts
-
AWS to create an ALv2-licensed fork of Elasticsearch and Kibana.
Yes. They linked to a bunch of the Github PRs they submitted in the article linked by the OP. " All changes to Elasticsearch were sent as upstream pull requests (#42066, #42658, #43284, #43839, #53643, #57271, #59563, #61400, #64513), and we then included the “oss” builds offered by Elastic in our distribution. This ensured that we were collaborating with the upstream developers and maintainers, and not creating a “fork” of the software. "
-
AWS announces forks of Elasticsearch and Kibana
For those, like me, who were curious and wanted to take a look: https://github.com/elastic/elasticsearch/blob/master/license...
Thank you! I had actually tried to find it after posting my comment and couldn't find it through their website. The day of the announcement Github hadn't been updated yet, and I gave up when I saw this didn't say where to look: https://github.com/elastic/elasticsearch/blob/master/LICENSE....
-
What can you do with Java?
Yep, ElasticSearch (and Lucene and Solr) are search engines that are written in Java!
-
Amazon: Not OK – why we had to change Elastic licensing
If I'm understanding correctly, most people/companies will want to use the Elastic License, which doesn't require any of the radical source code requirements of SSPL. However, if you can't meet the Elastic License requirements, such as if you're building an Elastic Cloud competitor, you are forced to use SSPL and abide by it.
Aside from not showing copies of the applicable licenses, it seems you have to read the code headers to determine which source file has which license. There are a lot of ways to respond to competitive threats from Amazon, but this approach is increasingly chaotic the closer you look.
[1] https://github.com/elastic/elasticsearch/blob/master/LICENSE...
Quoting another earlier comment from an elasticsearch thread here, credits to user _msw_ (https://news.ycombinator.com/item?id=25783509): https://github.com/elastic/elasticsearch/pull/61400 https://github.com/elastic/elasticsearch/pull/59563 https://github.com/elastic/elasticsearch/pull/57271 https://github.com/elastic/elasticsearch/pull/53643 .
None of the above appear to be related to AWS specific APIs and offer a small sample of total contributions from AWS employees.
The apache license, https://github.com/elastic/elasticsearch/blob/master/LICENSE...
-
Vinted Search Scaling Chapter 1: Indexing
The error above looks as though we simply sent too much data to Elasticsearch at once. Normally, this can be easily mitigated, for example by reducing the batch.size parameter in the connector or decreasing indexing concurrency. However, the error still didn't disappear. After some investigation we discovered that the problem was being caused by a bug in Elasticsearch client nodes.
-
Elasticsearch and Kibana are now business risks
The original announcement blog post Doubling down on open, Part II doesn't mention any exception for the client libraries and they're part of the https://github.com/elastic/elasticsearch repository in which everything will be relicensed.
Disclosure: I work for AWS, but I do not work directly on Elasticsearch related services.
Elasticsearch is/was an "upstream" for Open Distro for Elasticsearch (which is a distribution / collection of software). As an "upstream", changes to the core Apache 2.0 licensed software was sent as pull requests to Elastic, which are usually merged. It isn't correct to say that AWS has not been contributing to the upstream Elasticsearch code under an Apache 2.0 license (and, also, signing the CLA to boot, which allows Elastic to relicense AWS contributions under SSPL).
Here's a sample of PRs from AWS developers that I could find:
Stats
elastic/elasticsearch is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.