Why We Open Sourced RisingWave Under Apache 2.0 License
Join us in exploring the reasons, impact, and limitless potential that this transformative step brings to the tech community.
Join us in exploring the reasons, impact, and limitless potential that this transformative step brings to the tech community.
RisingWave, the distributed SQL streaming database, recently celebrated a significant milestone with the achievement of 1000 members in our Slack community. This event marks a momentous occasion for RisingWave, a project we have diligently worked on for the past three years.
From its initial release on GitHub under the Apache 2.0 license, RisingWave has garnered considerable attention, attracting numerous companies that have successfully deployed it in production to support real-time applications across diverse industries, such as manufacturing, e-commerce, fintech, SaaS, and more.
Many have inquired about our rationale behind open sourcing RisingWave under the Apache 2.0 license and questioned whether we plan to change the license in the future. We want to address these queries with utmost transparency.
Here are the top three reasons why we adhere to Apache 2.0 License:
From a commercialization standpoint, we have compelling reasons to open source RisingWave under the Apache 2.0 license. Contrary to concerns, this move does not harm our business but drives us to deliver an even better product to our customers. It is strategic:
Conclusion
As we approach the 2,000th community member, we anticipate even more remarkable progress and success in our mission to revolutionize stream processing for the benefit of all.
Sign up for our monthly newsletter if you’d like to keep up to date on all the happenings with RisingWave. Follow us on Twitter and Linkedin, and join our Slack community to talk to our engineers and hundreds of streaming enthusiasts worldwide.
Yingjun Wu
Founder and CEO at RisingWave Labs