Just my 2 cents. I don't care about Amazon's distro, I think it won't work. Others have tried, e.g. MariaDB vs MySQL, OpenOffice vs LibreOffice. Time will show though...
Edit: The thought was about big companies with their own agenda behind open source initiatives. Sorry about confusion.
What pattern are you seeing in those examples? Most Linux distros today ship with LibreOffice and have MariaDB in-repo. From where I sit, the open forks won.
Won in terms of user base, maybe. But in terms of money made and commercial adoption? Mysql beats Mariadb, though I can'
t say for openoffice/libreoffice.
Is that a fair metric to judge on? The entire point of forking MariaDB was that the developers expected Oracle to make compromises for the sake of money.
Yes, the fork timeline/direction is different, but imho, the pattern is, big companies with their own agenda, hiding behind "open" fork. I only can imagine the amount of resources put into keeping up. Will Amazon "rebase" their version with Elastic's? I doubt that for long time. Features advantaging AWS will be pushed, for better integration with 3rd party, which basically AWS' solutions.
I hope that people will be able to use "vanilla" ES too on AWS.
> big companies with their own agenda, hiding behind "open" fork.
MariaDB is a community fork away from a controlling company. Libreoffice is run by its own foundation, again after forking away from a company-controlled version.
> I hope that people will be able to use "vanilla" ES too on AWS.
I mean, worst case just run it on EC2/ECS, which lets you run anything you want. They're not going to break that.
I guess a big driver for me is a lot of the proprietary features (example: encryption in transit, RBAC, audit logging) seem absolutely basic to me. Not basic as in easy to implement, but basic as in as an operator I’ll need them for every type of logging/monitoring infra I’d ever spin up.
Worth noting I consider Elastic’s managed offering to be superior to AWS’ in a lot of ways. But personally I’ve always chosen to build my own setup off EC2
The difference is who is using them. In this case it's a trillion-dollar company that's also going to resell the fork as a service to their already locked-in customers. You betcha it's a threat to Elastic.
Edit: The thought was about big companies with their own agenda behind open source initiatives. Sorry about confusion.