Steve Jobs said something like Dropbox was a feature, not a product. I think Bezos feels the same about literally everything. AFAIK Azure/Google have actual partnerships with the Elastic stack, partnerships that assumedly benefit both sides and have staying power.
Part of me wonders if AWS always had planned to do this, and they were just waiting until it made business sense to fork (ie they had features and a new direction in mind but neglected to implement them because Elasticsearch was good enough as is). The alternative part is just 2 big corporations not finding a way to get along. Which means without clear direction and careful stewardship I'd expect the forks to just be cleanroom reimplementations or something like that.
> AFAIK Azure/Google have actual partnerships with the Elastic stack, partnerships that assumedly benefit both sides and have staying power.
Can you elaborate a bit here? We deploy from elastic.co into AWS and it seems to be fully supported. I'm not sure what they'd be doing with Google Cloud/Azure that they're not doing with AWS. Their homepage seems to still equate them all "Run where and how you want. Deploy on Google Cloud, Microsoft Azure, and Amazon Web Services with Elastic Cloud."
I may be wrong. I'm reading into this that was on HN the other day--
"We collaborate with cloud service providers, including Microsoft, Google, Alibaba, Tencent, Clever Cloud, and others. We have shown we can find a way to do it. We even work with other parts of Amazon. We are always open to doing that; it just needs to be OK."
https://www.elastic.co/blog/why-license-change-AWS.
I actually commented on that exact quote in the article to the same effect. I was kind of worried reading it that they plan to ditch the AWS integration tbh.. but at least for now I’m pretty sure it’s the same as the others.
> I think Bezos feels the same about literally everything.
That sounds weird. Comparing the "productization" of ES+Kibana to any AWS database stack is night and day. And not in AWS'es favor. ES and Kibana are much more of a product.
Part of me wonders if AWS always had planned to do this, and they were just waiting until it made business sense to fork (ie they had features and a new direction in mind but neglected to implement them because Elasticsearch was good enough as is). The alternative part is just 2 big corporations not finding a way to get along. Which means without clear direction and careful stewardship I'd expect the forks to just be cleanroom reimplementations or something like that.