Canonical joins the OpenSearch community (AWS-led fork of Elasticsearch)

twitter.com

53 points·frays··6 comments

Somewhat off topic, but I bet someone on HN that stumbles here will have relevant experience.

Is OpenSearch Dashboards (their Kibana fork) any good/is AWS being a good steward and moving it forward?

I ask because I’m in the process of updating some AWS infra in an org that uses Kibana. Our version is quite old and I’d like to upgrade both it & the ES storage layer to use newer APM features, etc.

I sympathize with Elastic’s position & their licensing change but as pragmatically I’d like to use an OpenSearch cluster and not be responsible for administering an ES cluster myself. But Kibana refuses to run pointing at an OpenSearch cluster.

So the question is, I guess, if I go all-in on OpenSearch does that seem like a sound long term choice? Alternatively, is Elastic.co’s cloud hosting competitive (from a run through their pricing calculator I think it would be more expensive)?

I would say yes, only because I’m tired of how dealing with vendor software has been going lately.

For example I’ve noticed Starburst and Confluent in particular only add useful scaling features to their paid product, rather than in the core. Same thing happened to nginx.

Also it’s a safe bet anyway since the managed AWS service isn’t going away any time soon.

Link to the post:

https://ubuntu.com/blog/canonical-opensearch-collaboration

Is there a reason for "why"?

Ubuntu is heavily used by AWS customers, Canonical sells support contracts for Ubuntu.

Kind or sad to see divide and conquer among independent open source ISVs

Reply on news.ycombinator.com