Re:AWS announces forks of Elasticsearch and Kibana
by chc on Thursday January 21, 2021 @06:06PM
(#25865859)
Amazon's forks will still be Apache-licensed, so if there's a tit-for-tat element here, it appears to be Amazon responding to Elastic's abandonment of open-source.
[ Parent
| on HN ]
Re:AWS announces forks of Elasticsearch and Kibana
by worldsayshi on Thursday January 21, 2021 @06:13PM
(#25865935)
Yeah, and here I feel that there's something missing in my description. While I think Elastics move is bad I definitely don't feel like Amazon is the good guy here either. I feel that there's a good chance that Amazon steam rolls Elastic and then five ten years away the community is worse off.
Re:AWS announces forks of Elasticsearch and Kibana
by Spivak on Thursday January 21, 2021 @07:02PM
(#25866462)
Open Source makes the most sense when your position is “I made this because it solved a problem I had and am giving it away so that it might solve problems for you.”
We might actually be better off with Amazon as the steward because they don’t need to make money on the software itself.
Re:AWS announces forks of Elasticsearch and Kibana
by worldsayshi on Thursday January 21, 2021 @07:12PM
(#25866547)
> need to make money on the software itself.
It would make a lot of sense for them to slowly close it down or modify it so that it eventually only makes sense to use it on their platform. Or something similar. And given what I've seen from their behaviour I would expect them to exploit whatever market leverage they can.
Re:AWS announces forks of Elasticsearch and Kibana
by liuliu on Friday January 22, 2021 @09:43AM
(#25872002)
What you described is exactly what Elastic doing now, and it triggers a fork. We will be fine if it happens again.
Re:AWS announces forks of Elasticsearch and Kibana
by glogla on Thursday January 21, 2021 @06:16PM
(#25865965)
Depends if they actually develop it. For other open source software, they usually keep improvements (say, improvements to Spark working with S3 from EMR, to give example from my area) to themselves in proprietary modules.