If you are Elastic, how could you compete against AWS even if it is your own software ?
Brand recognition should help. I also trust the original developers to build a better product than Amazon will on their fork.
AWS announces forks of Elasticsearch and Kibana
31–40 of 969 posts
Re: AWS announces forks of Elasticsearch and Kibana
#32The audacity of these AWS folks patronizing elastic about open source despite AWS making millions of dollars off of their open source project just reeks of entitlement. Glad I am never going to use AWS.
Re: AWS announces forks of Elasticsearch and Kibana
#33I would bet on AWS in this case as they will also likely have the support of anyone who wants to make a hosted service of those products. It will be interesting to see if eventually AWS starts making new APIs that diverge from the Elastic or if they chose to keep the product maintenance mode.
Re: AWS announces forks of Elasticsearch and Kibana
#34Amazon, ruining everyone's favorite open source apache projects one at a time.
Bezos is executing better than the original SAAS vendors that FOSS community editions. You want to compete with buff Jeff then make sure you support Azure/GCP too and can price below Bezos' margin above raw EC2 - usually means you have to get creative with spot instances and avoiding cross data center network.
Re: AWS announces forks of Elasticsearch and Kibana
#35>>> "This means that Elasticsearch and Kibana will no longer be open source software."
So any license which AWS cannot make good use of is not a valid OSS license? What a pirate logic here.
EDIT: I think I made a mistake here. SSPL is really a weird license here, not really friendly.
Re: AWS announces forks of Elasticsearch and Kibana
#36If you are Elastic, how could you compete against AWS even if it is your own software ?
Lower cost. AWS usually has huge premiums over the raw EC2/S3/EFS costs.
Better quality is a better answer. AWS charges a big premium for Elasticsearch and I don't think they'd drop their prices to try to squeeze Elastic - for one, it would be unlikely to even work - but even so it's always best to differentiate on being the better quality/"value" than the lowest cost.
Having used AWS Elasticsearch, it has a lot of deep problems with it in its current state so Elastic can compete on value just fine.
In other news, I think the Elastic licensing change beyond being ethically a dick move (legally it's their right), is just horrible business strategy. I said on this site several days ago that Amazon was just going to make an Apache 2.0 fork and keep chugging along, and that's exactly what we're seeing.
Re: AWS announces forks of Elasticsearch and Kibana
#37>Instead, new versions of the software will be offered under the Elastic License (which limits how it can be used) or the Server Side Public License (which has requirements that make it unacceptable to many in the open source community). I'm a bit out of the loop here, can someone please tell me why Elastic decided to enact this seemingly Anti-OSS license?
They couldn't compete with practically free (Amazon hosting their software as a service), and allegedly Amazon weren't commiting anything back into their repo.
Elastic appeared to make their money through hosting their own instances and selling professional licenses, which Amazon was in direct competition with.
Re: AWS announces forks of Elasticsearch and Kibana
#38Is the crux of the issue AWS is making money off ES and not paying Elastic a royalty (because the license doesn’t need it)?
If you don’t want that, maybe don’t open source your code with a license that allows others to do that?
Elastic are alleging that Amazon abused the Elasticsearch trademark and stole code from the proprietary (not open-source) part of their product.
> I took a personal loan to register the Elasticsearch trademark in 2011 believing in this norm in the open source ecosystem. Seeing the trademark so blatantly misused was especially painful to me. Our efforts to resolve the problem with Amazon failed, forcing us to file a lawsuit. NOT OK.
> We have seen that this trademark issue drives confusion with users thinking Amazon Elasticsearch Service is actually a service provided jointly with Elastic, with our blessing and collaboration. This is just not true. NOT OK.
> When the service launched, imagine our surprise when the Amazon CTO tweeted that the service was released in collaboration with us. It was not. And over the years, we have heard repeatedly that this confusion persists. NOT OK.
> When Amazon announced their Open Distro for Elasticsearch fork, they used code that we believe was copied by a third party from our commercial code and provided it as part of the Open Distro project. We believe this further divided our community and drove additional confusion.
Re: AWS announces forks of Elasticsearch and Kibana
#39If you are Elastic, how could you compete against AWS even if it is your own software ?
AWS is doing a terrible job with their es version. and es has aquired endgame and giving endgame away for 'free' with you purchase of es licensing, and the es stack run by es is getting a lot more attention and development that AWS version
Re: AWS announces forks of Elasticsearch and Kibana
#40And I, for sure, will never use them. The AWS version of ES has been abysmal- it’s only saving grace is that it’s “in the ecosystem”- I was convinced by an AWS zealot on my team. Never again.
I’ll second that. Complete pile of excrement. Edit: See my comment further down for an extrapolation. This one lacks merit which was a bad call on my part.
What exactly is wrong? And did you switch to something else?