Live data from Hacker News

OpenSearch: AWS fork of Elasticsearch and Kibana

aws.amazon.com

161–170 of 438 posts

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#161
post #137

Earlier quoted context omitted.

What may hurt them though, is the number of customers that currently feel things are currently "good enough". I don't know what their sales engagement looks like, so I'm not sure if this will really hurt them or not.

Perhaps! My money is on Elastic including an approximate nearest neighbor search in 8.0 which uses the new HNSW feature in Lucene 9, which is going to be hard to do in a distributed capacity and will be a significant feature if they can pull it off. PS - I've never seen gitsense before and it's really cool. I especially like the focus quadrant!

Since search is your domain expertise, I'll take your word for it :-)

As for GitSense, checkout the impact section and sort contributors by "First Commit". With this, you'll get a very good idea of the developer's expertise level.

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#163

Earlier quoted context omitted.

> Makes me wonder what these are for (copyright transfer) and why they decided it’s not needed. It also makes me wonder if this sort of thing has ever been taken/tested in court or if it’s paranoid friction with little value add. Some companies/projects might use them purely to avoid possible future legal headaches (I think GNU does this), and I'm not sure to what degree that has actually been tested, but they can al…

Indeed that is likely but I wonder why didn't they at least require a Developer's Cerificate of Origin [0] that kernel.org uses. This is really lightweight (just append one line to git commit message) and supposedly provides a minimum legal base for the change. IANAL. [0]: https://blog.chef.io/introducing-developer-certificate-of-or...

I just opened a pull request to fix a few typos in the README. They are requiring a Developer's Certificate of Origin.

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#164

Earlier quoted context omitted.

Indeed, although I'd say for a majority of situations, Amazon's hosted Elasticsearch service is a complete non-starter.

Why is it a non-starter? I have a few ElasticSearch clusters that have been running for years with zero effort/downtime/hassle.

What the other guy said.

Also my saying that is extremely colored by experiences with pre-ES6 versions, where AWS's offering didn't have many of the configuration knobs available that you really _need_ to operate a decent cluster.

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#165
post #102

Earlier quoted context omitted.

> But for ElasticSearch you’re stuck with them. I am a bit at a loss about that statement, you can run Elasticsearch on your on infrastructure

Quoting the comment you're replying to: > If OpenSearch is truely open then in theory you can find another provider Those are the key words. With an open source solution someone else can offer a turn-key solution that benefits from economies of scale.

Uh...can they? Who's going to benefit from more "economies of scale" than Amazon, Alibaba?

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#166

It's hard for me to know whether to feel bad for ES in this case. Did they bring it on themselves? Is Amazon too big and a bully? From my perspective, Amazon has made most of its profit price gouging consumers on bandwidth after vendor locking them into their ecosystem, where they bootstrap new services by wrapping open source software with some provisioning scripts, management dashboards and cookie-cutter API / cons…

> Amazon is not doing it for any altruistic reason

The beauty of OSS is that motives don't matter. If Amazon contributes and it's not detrimental in someway to the code, then it's a plus for anyone else who wants to use it.

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#167
post #43

Earlier quoted context omitted.

One thing which surprised me: Elastic has a market capitalization of ~$11B. I think that changes some of the more floaty ethical concerns. This is not a David vs Goliath situation. This is Goliath vs Super-Goliath. At this point, I'm much less interested in the drama of which mega-corp is screwing over the other. I'm more interested in: how does it affect me? When the titans are done trampling over the rest of us, wh…

Uhmmm I’m pretty sure David vs Goliath is talking about scale between competition. Saying that $11B is Goliath just because you’re sitting at $1M doesn’t mean they’re not in a crazy mismatched fight against a $2T company. In the same way you could be in a David vs Goliath situation yourself if you with $1M in wealth tried to sue someone with $25K of wealth. Everything is relative. Doesn’t mean it’s not a crazy unfair…

It may be relative but it isn't proportionate. A 11B market cap company can field a similarly competent legal department as a 2T market cap company can. I, with 25k, absolutely could not afford the same lawyer someone with 1M.

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#168

Is there any good that done by Amazon to support OSS? Like ever. They started with cloning MongoDB and now Elastic with actually zero contribution to the community regardless of their insane profits. This is a clear single. Amazon can always clone and redistribute any open source software then lock it in for AWS. If we've started to witness declining in OSS, well at least we know now who started the wave.

https://aws.amazon.com/opensource/

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#169

Earlier quoted context omitted.

You're asserting that they have forked OSS and then not provided back the source code for their own improvements. I guess we can check their github repos to see if that's the case.

As far as I know DocumentDB is closed source. Btw: I can name zero OSS projects from Amazon and this is not the same for Microsoft (VScode, TS) and FB (React, Jest).

Firecracker is a famous one that I can think of.

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#170

It's hard for me to know whether to feel bad for ES in this case. Did they bring it on themselves? Is Amazon too big and a bully? From my perspective, Amazon has made most of its profit price gouging consumers on bandwidth after vendor locking them into their ecosystem, where they bootstrap new services by wrapping open source software with some provisioning scripts, management dashboards and cookie-cutter API / cons…

It seems reductionist to say Amazon primarily wraps around open source. What about EC2? S3? Glue? DynamoDB? Many of the services that provide the most value are services Amazon has built out.
Post reply on HN