I had my own elasticsearch implementation in 2019 (on-prem) and my friend had the Amazon Elasticsearch Service. I enjoyed elastic and he hated it saying how it was a terrible product prone to failure. It wasn't until he opened a case with Elastic that he found out they had no control over the poor configuration being stood up in Amazon. This was one of the driving factors for Elastic to change the license since a couple years in court didn't yield any results in having the name changed. I mean, you have Elastic in other cloud ecosystems but AWS wouldn't play ball. Seems pretty obvious that AWS is the real issue and definitely the key driver in the Elasticsearch decision to change their license to cut AWS out. Litigation proves Elastic was not just trying to have an excuse to change license. They would be real dumb to pay millions in litigation when they could have just changed the license from the outset.
Although AWS is the least likely to do any good "for free", I tend to be on their side in this case, as Elastic used the liberal license for years to become big and famous while also "only" providing a frontend for lucene at first, if you will. And then after their plan worked out, they were like "nah, this liberal license made us big and successful, but now this software is monetized by others as its license explicitely allows. so we change it." They could have used a GPL-like license in the first place. Then this would have been a completely different story. So sorry - no sympathy for elastic, here.
elastic search is closed source because amazon literally copied it to make opensearch and started selling it.
Oracle Cloud also runs OpenSearch on their Search Service.
Aha, thanks Mark, good to know.
AWS is full of it. But so's every other company. So they can be proud to lead at yet something else.
I had my own elasticsearch implementation in 2019 (on-prem) and my friend had the Amazon Elasticsearch Service. I enjoyed elastic and he hated it saying how it was a terrible product prone to failure. It wasn't until he opened a case with Elastic that he found out they had no control over the poor configuration being stood up in Amazon. This was one of the driving factors for Elastic to change the license since a couple years in court didn't yield any results in having the name changed. I mean, you have Elastic in other cloud ecosystems but AWS wouldn't play ball. Seems pretty obvious that AWS is the real issue and definitely the key driver in the Elasticsearch decision to change their license to cut AWS out. Litigation proves Elastic was not just trying to have an excuse to change license. They would be real dumb to pay millions in litigation when they could have just changed the license from the outset.
Thank you! Great Video keep it up.
Thanks :). Glad you like it!
Although AWS is the least likely to do any good "for free", I tend to be on their side in this case, as Elastic used the liberal license for years to become big and famous while also "only" providing a frontend for lucene at first, if you will. And then after their plan worked out, they were like "nah, this liberal license made us big and successful, but now this software is monetized by others as its license explicitely allows. so we change it." They could have used a GPL-like license in the first place. Then this would have been a completely different story. So sorry - no sympathy for elastic, here.
where did you get data from at timestamp 8:28?
@felicia6242 Check db-engines.com/en/ranking
they got to pay the bills so can't blame them for charging. if customers need hand holding, these companies helping them should also get some revenue.
GRRRRRRRRrrrrrr, Amazon. :( Thank you for this analysis!
You're welcome! Let us know if we can be of any help with ES or OpenSearch @deborahspeece6838
are you sure that opensearch is aws specific?
@huseyinsenol1769 OpenSearch is absolutely not AWS-specific. It's maintained/developed by AWS, but you can run OpenSearch on your own, too.
@@Sematext oh ok, you were saying "as a service". realized now
Somehow it feels that's not your voice...
Hm, but it is. :) What do you mean?
Amazon is never in the right.
@christophjasinski4804 What's making you say that?