11–20 of 64 posts
Free, not open source version. Obviously a reaction to Amazon's fork- not wanting to give them any code to pull into their version. It will be interesting to see if this is enough to retain the majority of the userbase or if we'll still see a majority migrate to the 'Open Distro' fork.
Interesting. Three hours ago someone in our Ops team shared a link to "Open Distro for Elasticsearch" [1] and it's also featured on the AWS console login page. Is this a very rushed reaction to it? Or is this related? I would really love to have a clarification of what's happening in that space. [1] https://opendistro.github.io/for-elasticsearch/
It turned out that with the open core and premium-service models, the original company might not be the only one providing paid services or development. Which was a bit of a surprise to those original devs.
Free, not open source version. Obviously a reaction to Amazon's fork- not wanting to give them any code to pull into their version. It will be interesting to see if this is enough to retain the majority of the userbase or if we'll still see a majority migrate to the 'Open Distro' fork.
Interesting. Three hours ago someone in our Ops team shared a link to "Open Distro for Elasticsearch" [1] and it's also featured on the AWS console login page. Is this a very rushed reaction to it? Or is this related? I would really love to have a clarification of what's happening in that space. [1] https://opendistro.github.io/for-elasticsearch/
Free, not open source version. Obviously a reaction to Amazon's fork- not wanting to give them any code to pull into their version. It will be interesting to see if this is enough to retain the majority of the userbase or if we'll still see a majority migrate to the 'Open Distro' fork.
Too little too late? Trying to charge for TLS was a very poor move and it's made me not trust ElasticSearch...
I can understand they need to make money, but still a bit shady. Honestly though it's not something critical for my needs. Now if they could lower the resource hogging a bit, that would interest me... Maybe even pay for that.
The conclusion that I've reached is that the whole lucene model for logs is kind of outdated. Why am I tuning Java GC params to run "grep foo /logs". I think computers today can do fine with sharded flat files, a minimal index ("which node contains logs from pod foo-2387438-2384738 at 12:34AM"), and then just scale horizontally over (log messages, searches).
I hope my friends over at Tailscale are doing that and I can just move off ES entirely ;)
Too little too late? Trying to charge for TLS was a very poor move and it's made me not trust ElasticSearch...
Too little too late? Trying to charge for TLS was a very poor move and it's made me not trust ElasticSearch...
Why don’t you want to pay for a feature that you need? The company that pays your wages makes money from selling something. Of course you sell what people need
They could be using Elasticsearch for a side project. IMO, open source projects should not be unsecured.
Too little too late? Trying to charge for TLS was a very poor move and it's made me not trust ElasticSearch...
Why don’t you want to pay for a feature that you need? The company that pays your wages makes money from selling something. Of course you sell what people need
Free, not open source version. Obviously a reaction to Amazon's fork- not wanting to give them any code to pull into their version. It will be interesting to see if this is enough to retain the majority of the userbase or if we'll still see a majority migrate to the 'Open Distro' fork.
To be fair, the Docker Hub stats for the Open Distro for ES image don't show a very large shift away the Elastic ES image. And I doubt Amazon really cares about that, either. This is about whether their hosted ES service remains competitive with Elastic's hosted ES service.
I'm interested to see what Elastics next move will be.
grabs popcorn