<story><title>Elasticsearch is open source, again</title><url>https://www.elastic.co/blog/elasticsearch-is-open-source-again</url></story><parent_chain><item><author>Raed667</author><text>what is preventing AWS from dropping OpenSearch and going back to just selling Elastic ?</text></item><item><author>foxyv</author><text>It was so that AWS would create their own name for their fork:&lt;p&gt;&amp;gt; we changed the license, knowing it would result in a fork of Elasticsearch with a different name and a different trajectory. It’s a long story.&lt;p&gt;I think the name of the fork is now OpenSearch.</text></item><item><author>simonw</author><text>&amp;gt; The good news is that while it was painful, it worked. 3 years later, Amazon is fully invested in their fork, the market confusion has been (mostly) resolved, and our partnership with AWS is stronger than ever. We were even named AWS partner of the year.&lt;p&gt;I don&amp;#x27;t entirely understand this bit.</text></item></parent_chain><comment><author>godber</author><text>OpenSearch really appears to have a significant amount of development momentum.  It is functionally equivalent with Elasticsearch.  There would be no incentive for AWS to do this.  After ES broke their compatibility with OpenSearch they also broke compatibility with their own older versions.  This forced users to choose in order to move forward with anything.  I don’t know how it worked out for others but I’ve converted hundreds of ES clusters to OS and switched all development to OpenSearch because they started gaining momentum and didn’t make decisions that were actively hostile to their users.&lt;p&gt;Edit: As long as OpenSearch doesn’t start breaking the self hosted use case, I don’t see any reason to consider Elasticsearch again.  In fact, ES would have to offer up a significant advantage to overcome the bother.</text></comment>
<story><title>Elasticsearch is open source, again</title><url>https://www.elastic.co/blog/elasticsearch-is-open-source-again</url></story><parent_chain><item><author>Raed667</author><text>what is preventing AWS from dropping OpenSearch and going back to just selling Elastic ?</text></item><item><author>foxyv</author><text>It was so that AWS would create their own name for their fork:&lt;p&gt;&amp;gt; we changed the license, knowing it would result in a fork of Elasticsearch with a different name and a different trajectory. It’s a long story.&lt;p&gt;I think the name of the fork is now OpenSearch.</text></item><item><author>simonw</author><text>&amp;gt; The good news is that while it was painful, it worked. 3 years later, Amazon is fully invested in their fork, the market confusion has been (mostly) resolved, and our partnership with AWS is stronger than ever. We were even named AWS partner of the year.&lt;p&gt;I don&amp;#x27;t entirely understand this bit.</text></item></parent_chain><comment><author>foxyv</author><text>To be honest, the OpenSearch brand has more value now than Elastic.</text></comment>