Elastic’s Post

Elasticsearch is open source, again From the content: [D.N.A] Elasticsearch and Kibana can be called Open Source again. It is hard to express how happy this statement makes me. Literally jumping up and down with excitement here. All of us at Elastic are. Open source is in my DNA. It is in Elastic DNA....[read more] https://buff.ly/3T8JXRO Follow #techbeatly @techbeatly gmsocial, tbsocial

Great news for open source enthusiasts! 🎉 Elasticsearch and Kibana, the popular search and analytics engines, are officially open source again. The company Elastic has added AGPL as a licensing option, reaffirming their commitment to open-source principles. After a few years of using proprietary licenses due to challenges with AWS, Elastic is proudly returning to its open-source roots. This move provides clarity and choice to the community. As an open-source enthusiast, I applaud this decision by Elastic. Having Elasticsearch and Kibana available under AGPL fosters innovation and collaboration around these powerful tools. A win for the open-source world! Kudos to Elastic. #OpenSource #Elasticsearch #Kibana #AGPL #Innovation #ELv2 #SSPL

🚀 Big News for the Open Source and DevOps Community! 🚀 Elasticsearch and Kibana are officially Open Source again! 🎉 As someone who has used the ELK stack extensively in the past, I was genuinely saddened when it moved away from its open source roots. Like many others, I switched to OpenSearch, but it lacked some of the features that made ELK so powerful, such as advanced machine learning capabilities and Kibana's rich visualization options. Recently, Elastic announced that they’re adding AGPL as a licensing option alongside ELv2 and SSPL, meaning we can proudly call Elasticsearch Open Source once more. This is a fantastic development for those of us who value the open source ecosystem and the community that comes with it. I'm excited to see Elasticsearch back in the open source world, and I'm looking forward to diving back into it with all its powerful features intact. Kudos to Elastic for making this move! 🙌 Source: https://lnkd.in/d77F7ifs #Elasticsearch #OpenSource #ELKStack #TechCommunity #AGPL

Earlier this year in response to numerous requests for Elasticsearch integration, we’ve developed a technical solution to facilitate the integration of CrowdSec without native Elasticsearch support.  Check out our tutorial where we outline the method for connecting CrowdSec with the ELK stack- https://hubs.ly/Q02TpC0M0 #CrowdSec #syslog #ELKstack

In case you were on summer holiday and missed it: Last week #Elaticsearch was relicensed, again. Three years after Elastic took it off open source. I have to admit, their blog title got me excited. "Elasticsearch is open, again" Then I read the fine print. No, Elasticsearch isn't going back to its original Apache2 license (which it had used on its first decade). Instead it's adding an AGPL copyleft-style OSS license (on top of the two non-OSS ones) So is Elasticsearch open source? AGPL is Open Source Initiative (OSI) approved free and open source license. but is this enough, really, to regain the trust of the open source community? who guarantees they won't pull the rug again in a a couple of years? vendor-locking your OSS database? and making your OSS code contributions their commercial property? who assures that the community can contribute to the code indiscriminately? and keeps the open source codebase isolated from proprietary code, dial home, telemetry collection etc.? No, these are not made-up issues. These are real issues that the Elasticsearch community faced three years ago.  Ask the engineers who forked Elasticsearch to create the OpenSearch Project. Ask the engineers who had attempted to contribute to the Elasticsearch codebase the years before that. https://lnkd.in/dFrFT7e Seems Elastic wants to regain its open source status and stature, yet keep full ownership of the project. And when a single vendor owns an open source project, it owns all of the above. No checks and balances. Then, as the community adoption grows and starts looking lucrative, or when business slows down, the conflict of interest is inevitable. This is, in a nutshell, the reason vendor owned open source is an oxymoron. https://lnkd.in/duqJHQ5

"I, as a cynical Eastern European, hate almost everything in software. But I love Redis with a loyalty that I reserve for close friends and family and the first true day of spring, because Redis is software made for me, the developer." "In a pattern that has previously happened for Elasticsearch and Terraform, and one that was extremely predictable, Redis is now forked at least three different ways - the original Redis, now no longer under BSD, Valkey, under BSD and led by previous contributors to Redis from AWS and other companies, and Redict, under GPL, led by an open-source coalition. Both of these licenses allow commercial reuse. The old Redis was for developers. The new Redis is for enterprise sales, and for generative AI. It’s true that it’s not yet entirely clear what all of this means for the future of Redis the software." "But the problem is not only that the license changed suddenly, without warning, it’s the messaging behind the change, and the message is, even though there is extremely active community development, Redis is no longer in and of the community. We are no longer being consulted." "Good things don’t scale, except in the case of Redis, where all it does scale in O(1) time, but doesn’t align with the realities of markets in software." https://lnkd.in/gTJhfpQe by Vicki Boykis

White Widget’s case study got featured by the good folks at NeonDB! You’ve heard of serverless, but have you heard of serverless Postgres? We’re an early adopter, and this is our story. https://bit.ly/3wXMbM3

When we started with Apache Iceberg support, we made a commitment to support and push for open. We knew it would mean customers could more easily move in and out of Snowflake; in my view, this is a good thing, because it forces us to be the best platform, full stop. While we have been moving towards open, we have noticed a concerning pattern - the catalog is now becoming the new layer for lock-in in the lakehouse. That completely flies against our approach to Iceberg and our view of open. So we asked a radical question - why not develop an Iceberg catalog, that implements the Iceberg catalog APIs, push it into open source, and also use that catalog as our Iceberg catalog? Today I am *really* happy we can finally talk about that effort - Polaris. With Polaris, we want to do two things - (1) make sure customers don't get locked into a catalog and thus a platform; (2) make a very meaningful contribution to the OSS / Iceberg community. Turns out, we were also not the only ones thinking about this and are announcing it with some amazing partners who share our view. I want to express a BIG thank you to the Snowflake team and our awesome partners. https://lnkd.in/ggtbxmu6

Snowflake continues to build what is (actually) needed by customers instead of just integrating and operating mediocre features. This is fantastic!!! I have a customer that should be quite eager to adopt the Polaris catalog immediately (assuming they’re not locked into another catalog already). #snowflakedatacloud #snowflakedataengineer #snowflakeisanopenlake

🔥 Forgejo v9.0 is available ｢ Forgejo v9.0 is the first version to be released under a copyleft license, after a year of discussions. Among the motivations for this change is the realization that a pattern emerged over the years, exemplified by Redis, CockroachDB, Terraform and many others. They turned proprietary because people chose their own financial gain over the interest of the general public ｣ https://lnkd.in/d-dMWMFC #forgejo #git #opensource