Re:AWS announces forks of Elasticsearch and Kibana
by tsimionescu on Friday January 22, 2021 @05:36AM
(#25870383)
> If Elastic can offer better service to end-users, their deployment will be more popular and people will prefer their patches; if AWS can offer better service to end-users, their deployment will be more popular.
Not really, because Elastic doesn't get money from people using their free product. So, Elastic could theoretically go bankrupt even while providing an arbitrarily more popular ElasticSearch version.
AWS on the other hand is charging money for using their service, so they only need to compete with Elastic on the hosted version of ES. If their fork of ES is very hard to host on your own, that's a net benefit to AWS, regardless of how easy Elastic's fork is in the same scenarios - neither company is making money off the non-hosted version.
Re:AWS announces forks of Elasticsearch and Kibana
by pydry on Friday January 22, 2021 @05:31AM
(#25870359)
ES has to provide a much better service to win. Amazon can use their market power and vendor lock in to drive adoption of a worse service and squeeze out a better ES.
Network effects are great for behemoths but not so good for consumers.
Re:AWS announces forks of Elasticsearch and Kibana
by waheoo on Friday January 22, 2021 @08:33AM
(#25871492)
This is a job for antitrust, not licensing.
On the contrary, the commons gets the version of ElasticSearch that is most useful to end users. If Elastic can offer better service to end-users, their deployment will be more popular and people will prefer their patches; if AWS can offer better service to end-users, their deployment will be more popular.