Live data from Hacker News

Elasticsearch is open source, again

elastic.co

161–170 of 473 posts

Re: Elasticsearch is open source, again

#161
Too late. We just deployed a new project with OpenSearch after learning from an Elastic salesperson that their licensing fees would eat up significant portions of the projects profits. Also, since it's not spelled out clearly, I'm supposing huge parts of vital functionality are still subject to a paid license, even if the core functionality is technically open source now.

Re: Elasticsearch is open source, again

#163

Okay, cool. No notes, that's neat. Are there any SMEs that have worked with both OpenSearch (the fork) and ElasticSearch? Are there significant differences? I know the AWS fork had the big difference back then of having RBAC built into their Kibana portion.

Pure hearsay, but apparently ElasticSearch is considerably faster than OpenSearch. Would be good to compare the sources again, but I don't see any links to source on elastic.co yet.

Re: Elasticsearch is open source, again

#164
post #106

Earlier quoted context omitted.

Sounds to me like they're trying to cover up a bad case of regret. At our company we've fully shifted to OpenSearch, so there's no going back to ElasticSearch even if we wanted (not that we would want to). Also there is a lot of engineering contribution from Amazon that's seemingly gone now from Elasticsearch, right?

Sounds like you've fully shifted to exploiting (without contributing anything) to OpenSearch. I think Elastic will be just fine without your company or Amazon.

[dead]

Re: Elasticsearch is open source, again

#165
post #13

Earlier quoted context omitted.

To be honest, the OpenSearch brand has more value now than Elastic.

I see a couple people on here claiming this, but no data to back it up. Elastic beats out OpenSearch by a wide margin on every metric I've thought to check (gh stars, gh stars rate of increase, number of commits, number of pull requests opened, number of pull requests merged, number of issues, stack overflow questions...). Not a single one shows OpenSearch ahead. What metric are you using to come to the conclusion th…

[dead]

Re: Elasticsearch is open source, again

#166

Okay, cool. No notes, that's neat. Are there any SMEs that have worked with both OpenSearch (the fork) and ElasticSearch? Are there significant differences? I know the AWS fork had the big difference back then of having RBAC built into their Kibana portion.

https://www.elastic.co/blog/elasticsearch-opensearch-perform... https://www.elastic.co/search-labs/blog/elasticsearch-opense...

[I work for Elastic]

Re: Elasticsearch is open source, again

#167
post #13

Earlier quoted context omitted.

To be honest, the OpenSearch brand has more value now than Elastic.

I see a couple people on here claiming this, but no data to back it up. Elastic beats out OpenSearch by a wide margin on every metric I've thought to check (gh stars, gh stars rate of increase, number of commits, number of pull requests opened, number of pull requests merged, number of issues, stack overflow questions...). Not a single one shows OpenSearch ahead. What metric are you using to come to the conclusion th…

For one, we don't have to pay for basic amenities like security and alerts. To heck with gouging the customer for basic feature sets. Aws have their faults, but enabling teams to get the whole elastic experience without the weird nickle and diming is a blessing. Good on Amazon and boo elastic.

Re: Elasticsearch is open source, again

#168
post #156

Earlier quoted context omitted.

I'm not the GP, and I don't have a dog in this fight, but I think what they are complaining about is this sequence of events: - ElasticSearch was open-source - Amazon offered ElasticSearch open-source as a paid service - ElasticSearch was not happy about this and changed their license - Amazon forked ElasticSearch (the open-source version) and created OpenSearch based on that, continuing to serve OpenSearch - (Few ye…

What, when Amazon forked an open source project, as was allowed by the license, and continued to support that open source license even when the original company abandoned theirs? I’m not an Amazon fan, but they did the same thing (forking) that many others do, and they did it perfectly legally according to the license.

Yes, doesnt Elasticsearch do the same thing with Lucene?

https://stackoverflow.com/questions/27793721/what-is-the-dif...

AWS just offered a convenience layer over ElasticSearch

Re: Elasticsearch is open source, again

#169

Earlier quoted context omitted.

I see a couple people on here claiming this, but no data to back it up. Elastic beats out OpenSearch by a wide margin on every metric I've thought to check (gh stars, gh stars rate of increase, number of commits, number of pull requests opened, number of pull requests merged, number of issues, stack overflow questions...). Not a single one shows OpenSearch ahead. What metric are you using to come to the conclusion th…

For one, we don't have to pay for basic amenities like security and alerts. To heck with gouging the customer for basic feature sets. Aws have their faults, but enabling teams to get the whole elastic experience without the weird nickle and diming is a blessing. Good on Amazon and boo elastic.

This is a reason why you prefer it but not evidence that the brand has overtaken Elastic's.

Re: Elasticsearch is open source, again

#170

For use by businesses, the AGPL is a nightmare from my perspective. What does it actually require on behalf of a company using AGPL components? If I write my own library and link statically I need to release that? What about if I link it dynamically? What if the library is running on a separate machine and is separated by the network? I'm sure there will be people commenting in this thread that they understand exactl…

The AGPL is actually pretty clear:

> if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version

> To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.

Calling over the network is definitely not "adapting (...) in a fashion requiring copyright permission". While the AGPL might not be very much tried in court, copyright is.

Post reply on HN