Elasticsearch is open source, again
elastic.co
Elasticsearch is open source, again
1–10 of 473 posts
Re: Elasticsearch is open source, again
#2> 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.
I don't entirely understand this bit.
Re: Elasticsearch is open source, again
#3> 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. I don't entirely understand this bit.
I think they are saying when somebody looks to buy elastic search on AWS they find the Elastic offering on the market place and are not confused by the AWS offering that’s now called open search.
Re: Elasticsearch is open source, again
#4> 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. I don't entirely understand this bit.
It was so that AWS would create their own name for their fork:
> 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.
I think the name of the fork is now OpenSearch.
Re: Elasticsearch is open source, again
#5> 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. I don't entirely understand this bit.
It was so that AWS would create their own name for their fork: > 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. I think the name of the fork is now OpenSearch.
what is preventing AWS from dropping OpenSearch and going back to just selling Elastic ?
Re: Elasticsearch is open source, again
#6> 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. I don't entirely understand this bit.
It was so that AWS would create their own name for their fork: > 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. I think the name of the fork is now OpenSearch.
What could be learned from this example that might enable companies in the future to leverage trademark instead of a license change to accomplish the same thing? So much damage could have been avoided if this had been resolved differently to begin with.
Re: Elasticsearch is open source, again
#7Earlier quoted context omitted.
It was so that AWS would create their own name for their fork: > 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. I think the name of the fork is now OpenSearch.
what is preventing AWS from dropping OpenSearch and going back to just selling Elastic ?
sunk cost.
at least that’s what elastic seems to be betting on.
Re: Elasticsearch is open source, again
#8> 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. I don't entirely understand this bit.
It was so that AWS would create their own name for their fork: > 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. I think the name of the fork is now OpenSearch.
I don't understand why they didn't treat Amazon's previous offering as a trademark infringement.
Re: Elasticsearch is open source, again
#9Earlier quoted context omitted.
It was so that AWS would create their own name for their fork: > 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. I think the name of the fork is now OpenSearch.
what is preventing AWS from dropping OpenSearch and going back to just selling Elastic ?
Perhaps the fact that AWS has got years of time investment already made into OpenSearch and staying with their own version allows them to reduce risks should Elastic attempt to change ElasticSearch’s license again.
Re: Elasticsearch is open source, again
#10Okay, cool. No notes, that's neat.
Are there any SMEs that have worked with both OpenSearch (the fork) and ElasticSearch? Are there significant differences?
I know the AWS fork had the big difference back then of having RBAC built into their Kibana portion.