23 ms·
Apart from the general consternation about an OSS license becoming non-OSS, can we also talk about the problem that companies are formed, invest a whole lot of
by stavros 6y ago
Apart from the general consternation about an OSS license becoming non-OSS, can we also talk about the problem that companies are formed, invest a whole lot of resources into creating a product, open-source it, and then have Amazon eat into their profits by just installing and maintaining that product as a service?
No matter how you slice it, I think Amazon is bad for us end-users, and Elastic is good. Elastic could have released ES as closed source, but they didn't, and the OSS ecosystem is better for it. They were hoping to make money off their product, which I don't think anyone can fault them for, but instead Amazon came in and took a bunch of that money while not giving anything back.
Now Elastic is not happy, and I wouldn't be either. As an end user, I'm grateful the circumstances exist that allow companies to make a living from OSS, and I want to encourage that. AWS is the fly in the ointment there, and I don't see how blaming Elastic for not giving us stuff for free any more is anything other than entitled. We should be grateful that ES is OSS at all, and we should want an environment where companies that produce OSS can thrive, instead of blaming them for wanting to get paid for the work that they release freely into the world.
Amazon hinders that, period. I don't think Elastic is in the wrong here, I think Amazon is.
- delfinom 6y agoAmazon is executing EEE in modern times, it's brilliant nobody sees it. They are moving onto the "Extend and Extinguish" phase with elastic.
- VoxPelli 6y agoThey seems to be a lot better when it comes to cooperating with eg Envoy and Kubernetes communities though? Not sure how good they are with eg MySQL and PostgreSQL, anyone know?
- detaro 6y agocommunities is the key word. Neither have one company behind them whose income they are eating.
- dayjah 6y agoSorry, what is “EEE”? Brief search turns up a horse disease?
- detaro 6y agohttps://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
- mden 6y agoEmbrace, Extend, Extinguish. Infamous strategy of Microsoft esp in the 90s.
- delfinom 6y agoOne of the things Microsoft got anti-trusted for back in the day
- ec109685 6y agoElastic is a 10B company and have the ability to write all the proprietary code they want to compete with Amazon.
- paxys 6y ago$15B actually
- chikens 6y agoDon’t forget the CEO has cashed out ~$200M in stock the last two years alone and still holds $1B worth of stock, yet complains about AWS making money and changes the license so he can make even more. He likes to quote a tweet from 2015 from the CTO of AWS when they launched the Elasticsearch service in AWS. That was 6 years ago! They have had time to build a better offering with heir commercial licenses have failed. Elastic is trying to sell security now, what happens when they lose there too, change the license so any SIEM or analytics vendors have to pay them too? Elastic made a promise that the code would ALWAYS be Apache 2.0 and they went back on that promise, they lied to the community that helped build it, their customers, employees, partners and investors. The blog post about the license titles “Doubling Down on Open” is an insult to peoples’ intelligence, they are trying to play the victim because AWS is a mean bully. Well that’s business, if the CEO/founder didn’t see it coming then maybe he shouldn’t CEO? Take his billion dollars and go start something else and hand the company leadership over to someone who knows what they are doing.
- tootie 6y agoI don't see this at all. The "extinguish" phase is usually done when a product is acquired by a direct competitor to acquire it's customers. Amazon doesn't have a competing product. And their platform is well-known for supporting multiple competing software products (look at their array of databases for example). And the fact that they are now supporting their own JVM to protect users from Oracle's newly aggressive licensing. This is, perhaps, exploitation but it seems unlikely they'll kill Elastic ever.
- cortesoft 6y ago> Elastic could have released ES as closed source, but they didn't, and the OSS ecosystem is better for it. Except elasticsearch was created before the company Elastic even existed. They couldn’t have released it as closed source because they weren’t there to release it at all. It was written by one guy and it was based on previous open source code in Lucene. I am ok with them making money off their project, but it isn’t like they are owed a billion dollar company for their work.
- eloff 6y ago> I am ok with them making money off their project, but it isn’t like they are owed a billion dollar company for their work. Because no other companies build on a foundation of open-source software today? I think that describes every company. Yes, the actual core product is the open-source software, not just components of it, but does that really matter? I don't understand the distinction you're trying to make here.
- bcrosby95 6y agoComplaining about AWS building off open source software when you did too seems a bit awkward. I'd be willing to bet AWS has spent at least as many person-hours developing their service as has been put into ES itself. I don't really know where I fall on this subject. Companies need a route to monetize when developing open source products. It feels like AWS has been closing many ways to do that. Short term it might feel good for us end users, but long term it's probably bad for the ecosystem.
- cortesoft 6y agoMy distinction is that I don’t think they are being abused. They want to build a business around an open source tool just like AWS wants to also build a business around an open source tool. I am happy to let them compete to see who can offer the best value.
- SpicyLemonZest 6y agoThey actually have their billion dollar company, if they think they're owed it - Elastic has a market cap of over $14 billion.
- VoxPelli 6y agoI think both are at fault. Amazon for provoking this and Elastic for over-reacting like this and totally break with the open source licensing, when that isn’t necessary to stop Amazon. They could do like MariaDB rather than follow MongoDB: https://perens.com/2017/02/14/bsl-1-1/ https://perens.com/2017/02/14/bsl-1-1/ Would be much more appropriate and alienate the open source community much less.
- StavrosK 6y agoHmm, what's the difference between the BSL and Elastic's license?
- detaro 6y agoCode converts to an open-source license after X (e.g. 4) years in BSL. Time will tell how it works out, especially for mature products it could just mean that everyone targets the 4 year old version.
- VoxPelli 6y agoTime will also tell how eg. SSPL will work if eg. Elastic becomes bankrupt, what happens if I can't get a commercial license for it anymore in 10-20 years? BSL:s expire clause ensures that old code never gets unavailable because the business entity has vanished. Does SSPL have any similar protection?
- dhd415 6y agoNotably, they are apparently considering that: https://www.elastic.co/blog/license-change-clarification https://www.elastic.co/blog/license-change-clarification
- dumbfounder 6y agoAnd Elastic was built on top of Lucene. I slice it this way: as a company that is highly invested in AWS it is easier for us to deploy AWS ElasticSearch service than to use Elastic's cloud offering or set it up ourselves. But that doesn't mean I like it. Or are you talking about a different end user?
- StavrosK 6y agoYour options are "OSS ES that you can set up on your own for free" or "Closed source ES that you have to pay for". Not "Use AWS" and "Use Elastic".
- dumbfounder 6y agoI don't think of it that way at all. Nothing is free. The servers cost money. It costs money (resources) to manage servers. The cloud offerings appeal to us because we do not want to manage servers. AWS ES appeals to us because it is hard for us to sign contracts to buy software outside AWS. The trajectory of the software is definitely something we factor into the decision, but it is very often outweighed by the other factors. To me it is AWS Elastic vs Elastic Cloud vs hosting our own Elastic. Or use something else entirely.
- 0800LUCAS 6y ago> by just installing and maintaining that product as a service? You are seriously underestimating the value Amazon provides by "just installing and maintaining" those services. Maintaining a service at the scale they offer is a huge undertaking. You get the high-availability, the hundreds of engineers working to keep those services up and make them talk to other AWS services easily. You get teams of engineers on-call to react to any failures. I agree with you that this has a bad effect on the companies that originally created those projects, but I do see a huge value in what Amazon offers.
- StavrosK 6y agoI'm not saying "just" as in "it's easy". I'm saying "just" as in "they can install and maintain but don't have to develop it too".
- ignoramous 6y ago> ...they can install and maintain but don't have to develop it too. As someone building distributed systems, I'd think you'd appreciate that merely "installing" Elasticsearch wouldn't simply cut it for the scale AWS operates at. I wish Elastic would have focused on their differentiated offerings instead and had let go of their iron grip on Elasticsearch itself (perhaps by creating a Foundation around it).
- acatton 6y ago> Elastic could have released ES as closed source, but they didn't, and the OSS ecosystem is better for it. A relevant question is "would they have been that successful if Elastic were 'just another closed source enterprise product'." Elastic was successful because a lot of companies tried it out for free and then purchased licenses, or because hobbiysts used it on their personal project and then pushed for it at work.
- ardy42 6y ago> A relevant question is "would they have been that successful if Elastic were 'just another closed source enterprise product'." > Elastic was successful because a lot of companies tried it out for free and then purchased licenses, or because hobbiysts used it on their personal project and then pushed for it at work. That model is not actually incompatible with closed source. You can always distribute binaries with a liberal usage license. And if your model is selling support, that might actually be helpful, since it's even less practical for a 2nd or 3rd party to support software when they don't have access to the source code, so you'd sell more support contracts I think Amazon's behavior may end up just harming open source, by punishing the idealism that leads companies to try to make commercialized open source business models work.
- vinay_ys 6y agoYou would be surprised how many third party companies support closed source software product of another company. This is very common in enterprise world. It is also a common way for a vendor to get their foot into an enterprise entrenched with a competitor's product.
- ardy42 6y ago> You would be surprised how many third party companies support closed source software product of another company. This is very common in enterprise world. It is also a common way for a vendor to get their foot into an enterprise entrenched with a competitor's product. I'm aware of that, and have even worked with such companies. However, IMHO it's way harder (and less effective) than supporting an open source product. For instance, it's way harder for a 2nd or 3rd party to diagnose and patch a bug if they don't have the source.
- pjc50 6y agoThis is almost, but not quite, the "Tivoization" that prompted the creation of the GPL3. The requirement to give something back and/or avoid taking profit from the work of others is something the OSS world has a complicated relationship to. GPL is quite clear that there's a requirement to pass on source changes, if not explicitly to give them back, and many people were outraged by even this limited requirement and instead chose licenses which imposed no requirements at all. Similarly, people want their work to be used for free by everyone .. but haven't really considered that this results in them working for the Bezos fortune, for free. Or the US military, for free. There aren't simple clear answers to these questions, only a slowly evolving discussion.
- StavrosK 6y ago> There aren't simple clear answers to these questions, only a slowly evolving discussion. Certainly, and I think that if we want OSS to thrive we need to move towards a future where it's easy for companies to make a return on their investment by releasing OSS. I think Amazon and all the "I provide your software as a service" providers eat into that and hinder that future. Yes, GPLv3 was meant to fight Tivoization, but it never anticipated providers providing services on an OSS product without contributing significantly, in combination with the companies that develop the OSS hoping to make money off the same hosted service that the former undercuts. Basically, monetization strategies for OSS are few, and one that is beneficial for both the company and the consumer is providing hosted services. A third company that doesn't have to develop the software is usually a good enough competitor, but since the developer has the obvious support/knowledge advantage, they can still compete. This breaks down when Amazon comes in with its lock-in advantage and sucsk all the money away from the developer. This is why we're seeing these new licenses, because there's no way currently to be "OSS except Amazon". I think we do need to figure out some way.
- fakedang 6y agoI believe in a previous thread, someone suggested OSS except companies having this much of a revenue (since market cap is a bit of a variable metric). Why wouldn't that be a viable model?
- pythonaut_16 6y ago> Amazon came in and took a bunch of that money while not giving anything back Amazon took no money from them; they competed on potential revenues. I think people are upset, not because they don't clearly understand Elastic's motivations, but because Elastic is trying to paint Amazon as the bad guy for using the license Elastic offered. Amazon benefited from Elastic's open license, but so did Elastic. Being open source has greatly benefited Elastic's own business and growth. That isn't to say that Amazon's size and practices around open source aren't cause for concern, just that Elastic come across as very disingenuous when they try to lay all the blame on Amazon while proclaiming how dedicated they are to "openness".
- 35fbe7d3d5b9 6y ago> companies are formed, invest a whole lot of resources into creating a product, open-source it, and then have Amazon eat into their profits by just installing and maintaining that product as a service? Why should we be mad at Amazon for adhering to the terms of the license that the ES developers chose? Software isn't born under the terms of Apache 2/MIT/BSD/a similarly permissive license. The people who developed it chose that license.
- StavrosK 6y ago> Why should we be mad at Amazon for adhering to the terms of the license that the ES developers chose? We shouldn't. But you can't have your cake and eat it too, and say "well these are the terms you chose so why be mad at someone following them" and then ALSO say "hey, you can't change your terms!". They're their terms, they can change them if they want to.
- 35fbe7d3d5b9 6y ago> But you can't have your cake and eat it too, and say "well these are the terms you chose so why be mad at someone following them" and then ALSO say "hey, you can't change your terms!". I haven't said that. And as far as I know, Amazon hasn't either. Have I missed something from them? You seem to be the only person passing value judgements: > Amazon hinders that, period. I don't think Elastic is in the wrong here, I think Amazon is. This is incorrect: Amazon used Elastic per terms of the license. Elastic didn't care for an infringement on their business, so they've relicensed. No one is in the wrong here.
- StavrosK 6y ago> I haven't said that. And as far as I know, Amazon hasn't either. Have I missed something from them? I'm talking about the general sentiment here. Either Amazon have been playing by the rules and Elastic is within their rights to change those rules, so no problem anywhere, or Amazon has been harming a part of the OSS ecosystem and forced Elastic to make an unpopular change. > Amazon used Elastic per terms of the license Maybe I shouldn't have used "in the wrong" and said "is the problem" instead. I don't so much care about whether the rules are being followed as I care that more companies are encouraged to release their software as OSS because they can make money for it. That's a win-win situation to me.
- judofyr 6y ago> Apart from the general consternation about an OSS license becoming non-OSS, can we also talk about the problem that companies are formed, invest a whole lot of resources into creating a product, open-source it, and then have Amazon eat into their profits by just installing and maintaining that product as a service? Ten years ago I would be very hesitant adopting ElasticSearch if I knew that they were the only ones allowed to maintain a cloud solution of it. The fact that is was liberally licensed made me less afraid of vendor lock-in. In my opinion it seems like Elastic wants ElasticSearch to still be perceived as the fully open source project (with all of its good connotations) it once was. > AWS is the fly in the ointment there, and I don't see how blaming Elastic for not giving us stuff for free any more is anything other than entitled. We should be grateful that ES is OSS at all, and we should want an environment where companies that produce OSS can thrive, instead of blaming them for wanting to get paid for the work that they release freely into the world. It's okay to release things as non-OSS. It's also okay to release something as OSS first, and then regret later. But it's super weird that they're painting this picture of AWS being a big evil company when they're just doing exactly what is expected. Can't they just say "we're not able to build a company around the liberal license" instead of this "we're such an open company and we love open source and AWS is ruining everything" talk?
- tshaddox 6y ago> In my opinion it seems like Elastic wants ElasticSearch to still be perceived as the fully open source project (with all of its good connotations) it once was. That’s my attitude towards most of these license changes or “open core” pivots. These companies want all the good will and community contributions of “open source” while still being able to wield intellectual property protection laws against other companies who dare compete against them on unrelated, commoditized services like hosting.
- treis 6y agoIt's somewhere between bait and switch & dumping. It's very hard to compete against free. And it's very hard to make money when you give away your product for free. Cloud hosting was a way out of that conundrum. But that window is now closing as the big cloud operators move in + the rise of Docker making hosting much easier.
- ignoramous 6y agoElasticsearch became popular on back of being F/OSS. The "our code" Shay talks about is community's too: All the evangelizing through blog posts, talks; and the countless hours spent reporting bugs or even fixing them. If anyone thinks a community's contributions are any less than their own company's, then they don't get to claim to be torch-bearers of F/OSS (which Elastic is without realizing the irony). Shay keeps claiming "our users" aren't affected, but who's he fooling? They say, AWS cornered them to adopting dual-license SSPL, what's to say they woudln't do an Oracle in the future (like Sun did with Java and continue to do with their DB offerings?). Slippery slope, sure, but it is indeed slippery for a company struggling to compete with competition and seeking predatory avenues as last ditch attempt to stay alive. I believe, in all my naivety, that Elastic could have created an Elastic Foundation (like Joyent did with NodeJS, who btw didn't throw a hissy-fit at AWS for Lambda) and invited developers from all walks to shoulder the burden of the core software (which they themselves commoditized by F/OSSing it) so that they could focus on SaaS (like AWS). I'd like to think, Elastic's real problem is they have hard time competing with AWS in terms of pricing for SaaS (of course, AWS owns infrastructure and so it is a tough battle-front), but if they were paying any attention, AWS Elasticsearch Service was very poor in 2015 and continued to remain so for a long time (it sucks less now), but Elastic's own service wasn't up to the mark, either. I think they misplaced their priorities (see GCP's flawless execution with k8s, managed-k8s, and Anthos) and were caught asleep at the wheel when they could have captured SaaS market away from AWS in those interim years (2015-19) by focusing solely on differentiated features and not on the core Elasticsearch software (which was libre and hence undifferentiated). Of course, Shay and Elastic know better than I do and I am indeed a grumpy developer who's upset, but I want Elastic to give up their misleading messaging viz. 'doesn't affect / nothing changes for our users'. They're being hypocritical and not doing anyone any favours. > And to be clear, this change most likely has zero effect on you, our users. And no effect on our customers that engage with us either in cloud or on premises. No, Shay. It does affect the community, who are also the users of the software. > We created Elasticsearch; we care about it more than anyone else. It is our life’s work. We will wake up every day and do more to move the technology forward and innovate on your behalf. I see a lot of "We"s and "Our"s. And that's the problem with CLAs and stealing someone else's work. Companies can't tell anymore who's stealing from whom.
- tootie 6y agoFrom a purely utilitarian perspective, I can live without Elastic far easier than I could live without AWS. From a legal perspective, AWS are faultless in using OSS for their own purposes. The only losers are Elastic's investors. And there's no way they couldn't have seen this coming with their business model as it is.
- twobitshifter 6y agoI think Amazon infringed on the trademark. I’m not sure how that didn’t lead to an agreement between ES and Amazon. Perhaps Amazon just had the better lawyers.
- deleted 6y ago[deleted]
- ryanmarsh 6y agoOn the one hand I don’t like the idea of a company like Amazon exploiting (in the classic sense) open source. I’ve not seen Amazon give much back to open source relative to what they’ve gained. On the other hand if you open source something with a license that permits selling the software, well... what do you expect? You gotta hand it to Amazon. They’ve really hustled the industry by hosting open source code. The code is free, literally anybody else could have done this, but Amazon did it especially well.
- specialist 6y agoAmazon convinces investors to eschew profits. Unusual. Result: lower cost of capital. Amazon benefits from extended tax holiday. Result: lower cost of doing business. Amazon appropriates FOSS. Result: lower cost of development. Amazon knocks off successful products, competing with their own partners in their own walled garden. Result: lower cost of product development. Amazon allows counterfeit products, fake reviews, and other fraud. Result: lower cost of operations. Amazon uses gig workers. Result: lower cost of labor. I'm sensing a pattern... Amazon's success, their prime (pun!) advantage, is built on aggressively avoiding costs normally incurred by other businesses. They perfected WalMart's strategy. Sure, they've done some clever stuff. Throw enough spaghetti, some of it will stick. Free shipping with Prime membership is akin to Tencent's freemium (genius). And figuring out how to sell excess capacity was cool. I'm sure a lot of other leaders would share Bezos' tolerance for risk, commitment to long term plans, if only they weren't micromanaged by Wall St.
- remram 6y agoAny single entry on that "clever stuff" lists directly hurts someone and destroy the ecosystem in the long run.
- specialist 6y agoPoor phrasing on my part. I mean decisions which weren't obviously correct beforehand. I certainly didn't grok AWS for way too long. And there was plenty of concern trolling about free shipping, eg "how long can they sustain this loss leader?!". Very long when you have free capital, certainly more than anyone else. It fortuitously parlayed into amazing customer retention and upselling. What Prof G (Scott Galloway) has coined the rundle (recurring revenue bundle). Proved so effective, in fact, that everyone's now doing subscriptions for everything.
- astrange 6y agoGetting investors to give Bezos free money for being Bezos was actually pretty good for customers and got everyone free one-day shipping. Amazon is an investor charity like Uber, not a business.
- cratermoon 6y agoAmazon has become known for copying products and selling them as Amazon Basics. They either kick the original product off their platform or undercut the prices so drastically the original seller goes out of business. https://fortune.com/2016/04/20/amazon-copies-merchants/ https://fortune.com/2016/04/20/amazon-copies-merchants/
- tolmasky 6y agoI don't think there's "right" and "wrong", but bizarre (entitled?) expectations. A natural part of Open Source is that someone may come in and make way more money off of something than you do. In fact, Amazon makes way more money off of Linux than Linus ever did. But you don't even have to go that far, many completely unrelated YC companies made way more money off of Linux than Linus did, and could arguably have not pulled that off without Linux being a free OS that you don't even have to think about since it's so ingrained in hosting. But when the intent of Open Source is "to increase the quality of software around the world", this is considered a good result. However, when the intent of Open Source is some nebulous initial hyper-growth to then hope you can offer hosting, the expectations just aren't set correctly. Unfortunately, the open source strategy does not magically offer the right result based on the intent of the author. If Linus all of a sudden woke up tomorrow and said "Hey, I just realized that I'm not being paid a cut by literally every single company in Silicon Valley, that is NOT OK, I am going to shift gears and remove non-contributor code and start releasing Linux as closed source from now on", I feel people would be less forgiving than they are to these much less impactful companies. But Linus would be as "right" as they are, arguably more so. Many of these companies are simply learning that maybe all those "dinosaurs" of the 90s might have been onto something with commercial licensing, which ultimately seems to be what they actually want: to charge money for their software. Sure, it doesn't get you free contributions and ready-made communities, but it gets you money, which is what a company is supposed to do. And that's fine! It's just not Open Source.
- HotHotLava 6y agoLinus' original license did forbid making any money off the kernel: > - You may not distibute[sic] this for a fee, not even "handling" costs. Also I think the GPL was pretty important to the kernel, since many companies, especially in the 90s, probably would have kept contributions private and their code closed without that gentle push.
- pjmlp 6y agoWithout it, we would have all the big UNIXes still around, adopting BSD code as they already were doing.
- spullara 6y agoIf you ask me, these license changes are bait and switch. If they had started with this license it wouldn't have the same adoption, now they are pulling it.
- lacker 6y agoAmazon came in and took a bunch of that money while not giving anything back. Amazon is giving a lot back to the community, though. They are providing a really valuable service when they provide open source software as a service. They aren't giving back to Elastic the company, but it's important to note the difference, because Amazon isn't being a bad actor here. I think it's reasonable for both Amazon and Elastic to act the way they do, and I think the competition between their respective business models will end up in a better set of products available to developers.
- cmiles74 6y agoI would bet that if Elastic disappeared we'd see this offering stagnate. Amazon has put time and energy into work making the service but little (AFAICT) into the Elasticsearch product itself. In my opinion this is a short-sighted way for Amazon to do business. If Elastic makes every new feature unusable by Amazon, do to licensing restrictions, Amazon's product will fall behind.
- 7952 6y agoWould anyone consider licenses the specifically exclude certain companies?
- Doctor_Fegg 6y agoWTFPL effectively does that. Big companies won’t touch it.
- worik 6y agoThe point of Free Software is, in part, that other people can use it. That includes nice people like you and me It includes reprobates like Amazon The horrid games they were playing with trade marks is part of why Amazon is a reprobate.
- babarock 6y agoWhat's the point of "open sourcing" if you get annoyed at people redistributing your work? Honest question here. I'm really not interested to know who's in the "right" or in the "wrong". I want to know, what's the motivation for opensource if not "reuse my code please"
- StavrosK 6y agoThat question makes the wrong assumption. You assume "OSS" is a given and "getting annoyed at Amazon" is the issue. In reality, "getting annoyed at Amazon" is the given and "OSS" is the issue. Then, you can ask "if they get annoyed at Amazon, why open source?" and the answer is "indeed, and now that they realized their mistake they're changing it".
- growse 6y ago> Then, you can ask "if they get annoyed at Amazon, why open source?" and the answer is "indeed, and now that they realized their mistake they're changing it". Notably, they're changing it after building a business off the back of many contributors, many of whom expected to be contributing to OSS. Sure, there's a CLA so there's no legal issue, but I'm not sure it's any more morally virtuous than what Amazon's doing. Both are versions of "trying to make billions of dollars off the backs of other people's work". There's having cake, and then there's eating it. Either you want to retain control over something so you can monetize it to the max, or you want to particpate (and benefit from) the OSS community and build something that benefits everyone.
- tinyhouse 6y agoThe core of Elastic-search is Lucene, another OSS. I'm sure the ES team contributed a lot to Lucene, but do they share their profits with all the Lucene developers? You can think about Elastic as a hosted service around Lucene.
- nrmitchi 6y agoI've said this elsewhere, but no. There are two main differences here. 1. The scope of the change. My understanding is that Elasticsearch may use Lucene under the hood, but extends it in ways and for use cases that Lucene was not designed for. The same can not be said about AWS taking Elasticsearch and running it as a drop-in replacement. 2. Perhaps most importantly, Elasticsearch didn't build on top of Lucene, and then decide to call itself Lucene. If you think there is so little differentiation between the product you built and the product you built off of, that you are better off highjacking the name, then I question if you made any meaningful differences. 3rd BONUS difference: It is my understanding that a large part of the core Lucene team works at (or at one point worked at) Elastic[0]. [0] https://www.elastic.co/blog/investing-apache-lucene https://www.elastic.co/blog/investing-apache-lucene
- tinyhouse 6y ago1. No one says you need to modify/extend something in order to sell a service around it. That's why we have licenses that list exactly what you can do and cannot do with the software. 2. Amazon adds value here by providing hosting solutions for companies using the elastic search software. So it makes sense to call it "Amazon Elasticsearch Service" since that's what it is. I think interpreting this as Amazon built a new competing product but calling it the same name is not the right interpertation. If that's confusing then maybe modifying it to "amazon elasticsearch hosting service" would be the OK thing to do. Not sure if that would make Elastic happy. 3. That's nice of them (really!). Sounds like win-win. But again, it doesn't make anything they do more justifiable.
- cmiles74 6y agoThe only obligation that Easticsearch has to the Lucene project is to donate back improvements to Lucene itself. I believe the Elasticsearch project has done this in the past. No one is asking Amazon to share profits with Elastic. Many people do expect Amazon to honor trademarks of other companies. Many people expect Amazon not to package proprietary features as if they were free and open source. Lucene is a library that makes it easier to provide indexing and searching of "stuff". It's not a commercial product with a sales and consulting team. I can't think of a more apples and oranges comparison.
- nenolod 6y agoAmazon contributed code to Elasticsearch. They are certainly allowed to profit from their code contributions.
- iamsb 6y agoIs there a common theme that can be addressed by adding restriction which can stop distribution as a cloud service in MIT/other licenses? This is a question, and not a informed opinion/suggestion.
- Lazare 6y ago> No matter how you slice it, I think Amazon is bad for us end-users, and Elastic is good. I don't think that's clear. I (and the team I work with) use AWS, like so many of us do. (And the ones who don't very likely use Azure or GCP.) Why do we give money to AWS (and their kin) every month? I'd submit it's because we're getting value from it. If AWS was actually bad for end users then we, as end users, would walk away. If you were right, and AWS was bad and Elastic is good, this would be an easy problem. But actually, they're both good. The issue is people who paid AWS to host ES instead of Elastic, and you know who those people are? Us. And with reason!
- eins1234 6y agoI don't really want to get into the moral rabbit-hole of who's right and wrong as that's clearly super controversial and subjective. But I did want to add my personal anecdote to serve as a canary-in-the-mine on what effect the status quo could perceivably have on the proliferation of open source software over the long term: I think we can all agree on the basic premise that having more open source software is a good thing for society. For the longest time I dreamed of creating my own open source tools and products and simultaneously monetizing it to create a comfortable life for myself and maybe even eventually turning it into something bigger, and leave my mark on the world. However, as the years past and events like ElasticSearch v Amazon unfolded, I became more and more disillusioned on the realistic prospects of such an outcome. Today, I'm in the process of building something that would probably see more success in terms of adoption and do more good in the world if it's released as open source software, but at this point I've basically made up my mind to release it as proprietary software to have a realistic shot of monetizing it to achieve financial independence and eventually build a company around it. Basically I've weighed the tradeoffs and chose to put my own ability to capture the value of what I created over trying to maximize the value my software could create if open sourced. This was not a easy decision for me to make, but I suspect I'm not alone in having thought about these tradeoffs and reaching these same conclusions. And as more and more people witness the struggles of companies trying to build viable businesses on top of open source software, more and more people could make the same decision, and thus society would be robbed of all the value that having these pieces of software as open source could have created. I think the chilling effect these kinds of case studies have on the proliferation of new open source software, and the loss incurred by society as a whole as a result, is at the core of what we should be trying to figure out a solution for, not some philosophical discussion around who's in the right or wrong.
- closeparen 6y agoIf not AWS it could have been anyone. This is an inherent vulnerability in the open source business model: there's no particular reason that upstream developers would be the best at hosting or consulting on their own stuff. You can afford to give the client more attention/hardware for their money if you don't have to also pay developers.
- sriku 6y agoThere are other products that are at similar enough risk that this angle should be taken seriously - ex: https://dgraph.io https://dgraph.io and https://materialize.com https://materialize.com .
- goatinaboat 6y agoAWS is the fly in the ointment there No, many SaaS providers have discovered that it’s the back door in the GPL, Google were the leaders in this field. AWS is egregious but they didn’t invent doing this.
- finikytou 6y agoYour argument that Elastic could have released ES closed source and did us a favor is not a valid one. They released ES open source so that they could leverage the community + an open source tool (lucene) to build their tool and later on their company. If not for the open source they would be just a random actor in search and SOLR would likely be a better tool than it is now. Also by your logic elastic did to lucene what aws did to elastic...