-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
MeiliSearch
A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
-
security
🔐 Secure your cluster with TLS, numerous authentication backends, data masking, audit logging as well as role-based access control on indices, documents, and fields (by opensearch-project)
Disclosure: I work for AWS.
There were contributions sent upstream for Elasticsearch bugfixes and enhancements. Some of those PRs are still open, for example [1].
A sampling of additional PRs can be found in this blog post [2].
Further contributions upstream to Apache Lucene have been growing over the years. The new Approximate Nearest Neighbor support in Elasticsearch 8.0 comes from work that was sponsored by Amazon in upstream Apache Lucene [3].
[1] https://github.com/elastic/elasticsearch/pull/64513
[2] https://aws.amazon.com/blogs/opensource/stepping-up-for-a-tr...
[3] https://issues.apache.org/jira/browse/LUCENE-9004
For anyone who wanted out of this fiasco, checkout MeiliSearch: https://docs.meilisearch.com/
It's written in asynchronous Rust, so it's fast and scales well on multithreaded. Downside is that it does not have distributed mode yet, but it is scheduled on this year (presumably Q4 2022 I guess)
I think part of the challenge looking at these metrics is the project versus repo structure. For instance, contributions to security are included in the elasticsearch repo but not in the core OpenSearch repo e.g. https://github.com/opensearch-project/security/graphs/contri...
But I still think having a bunch of folks contribute isn't trivial and worth highlighting (57 is a ton for many projects) and anytime I see a truly OSS project at this scale I think it's a good thing.