3 ms·
Your moral position is based on market capitalization? The core piece of ElasticSearch's technology is Lucene, an open soure project. Elastic the company uses
by ctvo 8y ago
Your moral position is based on market capitalization?
The core piece of ElasticSearch's technology is Lucene, an open soure project. Elastic the company uses this open source work to become a 5 billion dollar company.
The core piece of AWS's ES service is ElasticSearch, an open source project. Amazon the company uses this open source work to further enrich themselves.
Amazon is bad because they're a 1 trillion dollar company. Elastic is OK because they're a 5 billion dollar company.
- blazespin 8y agoYes, the whole argument is based on anti trust. Did you not read the article?
- majewsky 8y agoPlease don't insinuate that someone has not read the submitted article. You could rephrase this, for example, like this: > Yes, the whole argument is based on anti trust, as the article explains.
- mgoetzke 8y agoI get where you are coming from, but Lucene is a building block, a library and cannot be immediately used as a valuable service. ES can be used by quite high level developers to implement scalable solutions. Building blocks and libraries offering convenience are not as valuable on its own than solutions that offer some quite immediate value at a reasonably high level. Even if from an abstract view both still require developers as users the applicability is quite different. Amazon cannot 'host' lucene as a service per se. Services vs Libraries
- geezerjay 8y ago> I get where you are coming from, but Lucene is a building block, a library and cannot be immediately used as a valuable service. ES can be used by quite high level developers to implement scalable solutions. Your argument makes no sense. Even if we accept the thesis that building block components are up for grabs because they cannot be immediately used as valuable services... Well, neither can services. You need to design a system architecture, figure out how and if a component plays a role, pick a component, config the component, setup a deployment ans scaling strategy, config and integrate metrics and health checks, ingest data, monitor the service, etc etc etc. And if we actually want to make an objective comparison between libraries and services... Well, in the end they are all components of a larger system. So, obviously there is no objective distinction. There's only intellectual property and companies being hypocrite wanting to have their cake and eating it too. They can't get it both ways.
- AsyncAwait 8y agoThe difference, I feel, is that Amazon's solutions are not even open-core. They're straight up closed-source, which I think is objectively worse.
- 013a 8y agoTheir elasticsearch fork is literally called Open Distro for Elasticsearch. Its totally open, and all licensed as Apache 2.0. Their mongodb clone isn't. It'd be kind of cool if it was, but there's substantial evidence its based on the Aurora Storage engine. Through the docs and various talks at Re:Invent, its clear that the ASE is insanely coupled to AWS, with tight integration to S3 and deep availability-zone awareness. It would be useless beyond an academic exercise to someone who isn't on AWS. It would be cool to see it all open sourced, but not really valuable. AWS has a pretty strong history of open source in the cloud space, such that it feels strange to me that people still think they're an "enemy" or something. Not as strong as Google or Microsoft, but they're certainly not a New Oracle or anything. You should check out their Open Source Blog [1], and notice that new posts are made literally every two days. [1] https://aws.amazon.com/blogs/opensource/ https://aws.amazon.com/blogs/opensource/