Is Amazon's AWS Approaching 'War' for Control of Elasticsearch?

Long-time Slashdot reader jasenj1 and Striek both shared news of a growing open source controversy. 'Amazon Web Services on Monday announced that it's partnering with Netflix and Expedia to champion a new Open Distro for Elasticsearch due to concerns of proprietary code being mixed into the open source Elasticsearch project,' reports Datanami.

'Elastic, the company behind Elasticsearch, responded by accusing Amazon of copying code, inserting bugs into the community code, and engaging with the company under false pretenses...'

In a blog post, Adrian Cockcroft, the vice president of cloud architecture strategy for AWS, says the new project is a 'value added' distribution that's 100% open source, and that developers working on it will contribute any improvements or fixes back to the upstream Elasticsearch project. 'The new advanced features of Open Distro for Elasticsearch are all Apache 2.0 licensed,' Cockroft writes. 'With the first release, our goal is to address many critical features missing from open source Elasticsearch, such as security, event monitoring and alerting, and SQL support....' Cockroft says there's no clear documentation in the Elasticsearch release notes over what's open source and what's proprietary. 'Enterprise developers may inadvertently apply a fix or enhancement to the proprietary source code,' he wrote. 'This is hard to track and govern, could lead to breach of license, and could lead to immediate termination of rights (for both proprietary free and paid).'
Elastic CEO Shay Banon responded Tuesday to AWS in a blog post, in which he leveled a variety of accusations at the cloud giant. 'Our products were forked, redistributed and rebundled so many times I lost count,' Banon wrote. 'There was always a 'reason' [for the forks, redistributions, and rebundling], at times masked with fake altruism or benevolence. None of these have lasted. They were built to serve their own needs, drive confusion, and splinter the community.' Elastic's commercial code may have provided an 'inspiration' for others to follow, Banon wrote, but that inspiration didn't necessarily make for clean code. 'It has been bluntly copied by various companies and even found its way back to certain distributions or forks, like the freshly minted Amazon one, sadly, painfully, with critical bugs,' he wrote.

Read more of this story at Slashdot.