← Back to context

Comment by bombcar

4 years ago

When there are two large entities (and I take this to mean way larger than you or your company) then you’re better off rooting for the one that at least releases code you can use.

If OpenSearch is truely open then in theory you can find another provider. But for ElasticSearch you’re stuck with them.

31 comments

bombcar

Reply
kfir  4 years ago

> 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

  • mixedCase  4 years ago

    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.

  • virgilp  4 years ago

    That is not entirely true, of course. Not if you don’t want to pay. As proof - just look at Amazon, they can’t (that’s why they forked it).

    • mikepurvis  4 years ago

      I don't think it's the freedom to run it anywhere. It's the freedom to run it anywhere and make changes to it that you don't contribute back:

      1. Amazon wants to make private changes to the management layer for their cloud offering and not share those.

      2. ES doesn't want that, so the 7.11+ license restricts it.

      3. Amazon doesn't want to have to explain to their customers why their ES offering is stuck on v7.10, so they're changing the name of it.

      4. Elastic was really hoping this wouldn't happen, but they overestimated the value of their brand and Amazon called their bluff.

      So yeah, nominally OpenSearch is unrestricted, but realistically few other entities are in a position to make or benefit from the private modifications Amazon will be making. For us normal people, ES and OS are equivalent today, so it's more about how they're going to diverge over time in terms of fixes, features, whatever.

      25 replies →