Shay Banon

And when it gets to a point where Amazon Elasticsearch exists for enough years, it becomes a fact whether they end up changing their name or not.

And when it gets to a point where Amazon Elasticsearch exists for enough years, it becomes a fact whether they end up changing their name or not.

Exactly.

Exactly.

Yes, and especially when it wasn't even it's Amazon's Elasticsearch version or something like that. It's done in partnership with Elastic, right? Like that was the additional layer of confusion that kind of like made it really big. And that was really confusing to users because it's like, because if I naively look at it from the outside and I go Amazon Elasticsearch, you go like, oh, amazing.

Yes, and especially when it wasn't even it's Amazon's Elasticsearch version or something like that. It's done in partnership with Elastic, right? Like that was the additional layer of confusion that kind of like made it really big. And that was really confusing to users because it's like, because if I naively look at it from the outside and I go Amazon Elasticsearch, you go like, oh, amazing.

Elastic managed to do partnership with Amazon and they take Elasticsearch and provide it as a service and I'll go and use that. And, you know, we all think that we live in hacker news on Twitter or something like that, but most users don't. They just go and say, oh, Amazon's Elasticsearch. I'll just go and use that.

Elastic managed to do partnership with Amazon and they take Elasticsearch and provide it as a service and I'll go and use that. And, you know, we all think that we live in hacker news on Twitter or something like that, but most users don't. They just go and say, oh, Amazon's Elasticsearch. I'll just go and use that.

And they don't understand the nuances or the fact that it's not us or something along those lines. And, you know, nothing bad with Amazon as well. You know, they're a great partner of us now and we work well and actually think that Amazon matured a lot in how they run their cloud versus the early days. But we just felt like we had to make a difference and that's where we landed.

And they don't understand the nuances or the fact that it's not us or something along those lines. And, you know, nothing bad with Amazon as well. You know, they're a great partner of us now and we work well and actually think that Amazon matured a lot in how they run their cloud versus the early days. But we just felt like we had to make a difference and that's where we landed.

Yeah, we changed it actually to two licenses that you could choose from. The SSPL one that MongoDB changed to. So MongoDB did that change as well. Or a license that we wrote that was more in the Apache type. You know, there's kind of like two families of licenses. We call it the Elastic License V2. It's actually a very, very simple license.

Yeah, we changed it actually to two licenses that you could choose from. The SSPL one that MongoDB changed to. So MongoDB did that change as well. Or a license that we wrote that was more in the Apache type. You know, there's kind of like two families of licenses. We call it the Elastic License V2. It's actually a very, very simple license.

And we allow users to choose between them because some were concerned about the SSPL, someone concerned about the Elastic License V2. We kept all of our code open. We kept all of our free stuff free. We just didn't call it open source. Nothing changed except for the license, if that makes sense.

And we allow users to choose between them because some were concerned about the SSPL, someone concerned about the Elastic License V2. We kept all of our code open. We kept all of our free stuff free. We just didn't call it open source. Nothing changed except for the license, if that makes sense.

First of all, I was very sad and it was painful. And, you know, as someone that loves open source and believes in it, that was a sad thing not to be able to call it open source. And I agree, by the way. I think if I understand things correctly, we could have called ourselves open source because there's nothing illegal by calling ourselves open source.

First of all, I was very sad and it was painful. And, you know, as someone that loves open source and believes in it, that was a sad thing not to be able to call it open source. And I agree, by the way. I think if I understand things correctly, we could have called ourselves open source because there's nothing illegal by calling ourselves open source.

But I believe in the social contract of open source and OSI. And we stood by it and we changed our name and we, you know, search and replace all open source with free and open and other stuff. And that was not great. Our usage, interestingly, you know, we live in our own like bubble of interest and, you know, and things like that. Our usage didn't change that much to be completely honest.

But I believe in the social contract of open source and OSI. And we stood by it and we changed our name and we, you know, search and replace all open source with free and open and other stuff. And that was not great. Our usage, interestingly, you know, we live in our own like bubble of interest and, you know, and things like that. Our usage didn't change that much to be completely honest.

So the usage of Elasticsearch continued to grow. People just like downloaded the Elasticsearch and used it and ran it and it was free and using it for search and all the other use cases that people use it for. But we were still not called open source. And I think open source matters a lot. And we always hope that we will be able to get back to open source.

So the usage of Elasticsearch continued to grow. People just like downloaded the Elasticsearch and used it and ran it and it was free and using it for search and all the other use cases that people use it for. But we were still not called open source. And I think open source matters a lot. And we always hope that we will be able to get back to open source.