4 ms·

This GitHub repository is just the database, what about the code that holds together their cloud resources? I was not able to find it. They criticize AWS for m

by mpsq 6y ago

This GitHub repository is just the database, what about the code that holds together their cloud resources? I was not able to find it. They criticize AWS for making money on Elasticsearch for example, AWS is "taking advantage of the R&D efforts of others". So Amazon is making money on a "serverless" / cloud experience. At the same time, it is known that Amazon is contributing back to Elasticsearch [1]. To that regard, I find their business model really similar to the one AWS is relying upon. [1] https://www.techrepublic.com/article/aws-contributes-to-elasticsearch-and-critics-say-its-kneecapping-competitors/ https://www.techrepublic.com/article/aws-contributes-to-elas...

rattray 6y ago
Huh? If I want to run someone else's software on my cloud, how I want to do that depends on my cloud. I want docs and binaries, not a full cloud configuration. Some people would want k8s, some docker swarm or whatever, some an aws config, others ansible, etc etc etc. If I want a managed service, I _want_ to pay for that. The price includes people responding to pages and fixing problems, as well as fiddling with configs. And I'd much rather be paying that money to a small (relatively) open-source company than a behemoth like AWS.
- sirffuzzylogik 6y ago
  > If I want a managed service, I _want_ to pay for that. The price includes people responding to pages and fixing problems, as well as fiddling with configs. Is this not what S3 is? You are free to use Elasticsearch and handle everything yourself, but if you want a managed service, you can use AWS. They are "attacking" the S3 offering, I still struggle to see any difference with them hosting Postgres. > And I'd much rather be paying that money to a small (relatively) open-source company than a behemoth like AWS. I am 100% with you on this, I do not want to defend AWS nor do I want to promote their products. The vendor lock-in situation you are in when using AWS is pretty bad and quite scary... An yes, I agree that the way they monetize open-source software is questionable.
dhd415 6y ago
There's no way that Elastic would accept the Open Distro features as a contribution to Elasticsearch because they include inferior versions of features already available in the commercially-licensed version of Elasticsearch and, in the case of the Search Guard code in Open Distro, code that Elastic alleges was lifted from existing commercially-licensed Elasticsearch features. AWS knows all this but offers it anyway as a PR stunt so they can say that they at least attempted to make contributions to Elasticsearch.

by mpsq 6y ago

rattray 6y ago

Huh? If I want to run someone else's software on my cloud, how I want to do that depends on my cloud. I want docs and binaries, not a full cloud configuration. Some people would want k8s, some docker swarm or whatever, some an aws config, others ansible, etc etc etc. If I want a managed service, I _want_ to pay for that. The price includes people responding to pages and fixing problems, as well as fiddling with configs. And I'd much rather be paying that money to a small (relatively) open-source company than a behemoth like AWS.

sirffuzzylogik 6y ago
> If I want a managed service, I _want_ to pay for that. The price includes people responding to pages and fixing problems, as well as fiddling with configs. Is this not what S3 is? You are free to use Elasticsearch and handle everything yourself, but if you want a managed service, you can use AWS. They are "attacking" the S3 offering, I still struggle to see any difference with them hosting Postgres. > And I'd much rather be paying that money to a small (relatively) open-source company than a behemoth like AWS. I am 100% with you on this, I do not want to defend AWS nor do I want to promote their products. The vendor lock-in situation you are in when using AWS is pretty bad and quite scary... An yes, I agree that the way they monetize open-source software is questionable.

dhd415 6y ago

There's no way that Elastic would accept the Open Distro features as a contribution to Elasticsearch because they include inferior versions of features already available in the commercially-licensed version of Elasticsearch and, in the case of the Search Guard code in Open Distro, code that Elastic alleges was lifted from existing commercially-licensed Elasticsearch features. AWS knows all this but offers it anyway as a PR stunt so they can say that they at least attempted to make contributions to Elasticsearch.