Thoughts On Moving Debezium to the Commonhaus Foundation
If you are following the news around Debezium—an open-source platform for Change Data Capture (CDC) for a variety of databases—you may have seen the announcement that the project is in the process of moving to the Commonhaus Foundation. I think this is excellent news for the Debezium project, its community, and open-source CDC at large. In this post I’d like to share some more context on why I am so excited about this development.
Debezium was founded in 2016 by Randall Hauch, back then a software engineer at Red Hat. Pretty much from the get go, the Apache-licensed project attracted a very diverse community not only of users, but also of contributors. The Debezium development team has been doing an amazing job of fostering a welcoming and open environment, establishing a level playing field for contributors from Red Hat—who funded and continues to fund the salaries of the core team working on the project, including mine, while leading Debezium between 2017 and 2022—as well as other organizations alike. Companies such as Google, IBM, Stripe, Slack, WePay, SugarCRM, Instaclustr, Bolt, and many others have put substantial resources into the project. More than 650 individuals have contributed to the project at this point, ranging from small fixes and improvements, over developing complete features in the Debezium core framework, all the way up to driving the work and roadmap of specific connectors.
Of course I am biased, but I think it’s fair to say that when it comes to "vendor-owned" open-source, Debezium has been a tremendous success. When the project website says the following, it’s truly meant like that and not just empty words:
The Debezium project is operated as a community-centric open source project. While Red Hat product management has a voice, it is akin to the same voice of any member of the community, whether they contribute code, bug reports, bug fixes or documentation.
The community has truly lived up to this aspiration and the project has always managed to align the interests of the different parties involved (I only remember a single time where there was a continued discussion about a specific feature and its implementation between the core team and the contributing team, with the idea of forking the project being floated briefly). Nevertheless, ultimately the Debezium project was controlled by a single entity, Red Hat. They owned the name, the domain, the GitHub organization, social media channels, etc. Despite the continued demonstration of best intentions, some folks may have had reservations to contribute to a project managed like that.
That’s why I was thrilled to learn that several other projects sponsored and managed by Red Hat, for instance Quarkus and Hibernate, announced their move to the Commonhaus Foundation earlier this year. This foundation acts as a 100% neutral home of open-source projects, addressing any potential concerns around ownership which contributors may have. I was hoping for Debezium to make the move to Commonhaus as well, and I could not have been any happier when learning a few weeks back that it actually is going to happen.
The Commonhaus Foundation is a particularly interesting instance of an open-source foundation, as it provides its projects with an extensive degree of freedom. Quoting their FAQ, what Commonhaus differentiates from other foundations such as Apache Software Foundation, Eclipse Foundation, or Linux Foundation, is this (check out the full FAQ for comparisons with specific foundations):
The Commonhaus Foundation sets itself apart by providing open source projects with a unique combination of autonomy and tailored support, adapted to their specific stages of development and needs. By simplifying access to funding and offering a stable, long-term home for their assets, the Foundation enables projects to govern themselves and leverage collective resources for greater visibility and impact.
Unlike the structured environments and specific licensing and infrastructure requirements characteristic of foundations like the Apache and Eclipse Foundations, Commonhaus allows projects to maintain their established brand, community identity, infrastructure, and governance practices. It also supports a broader array of OSI-approved licenses.
The way I perceive it, Commonhaus is a "No frills" foundation, a neutral project home which acts as the owner of IP such as project trademarks, helps projects with financial management, provides them with infrastructure for receiving donations (something we always struggled with during my time leading the project), and more. But it stays out of projects day-to-day operations as much as possible. I believe it’s a perfect fit for a project like Debezium, with a strong existing community, brand, and established processes. Debezium is going to join the ranks of other popular projects under the Commonhaus umbrella, such as SDKMan, OpenRewrite, and Jackson. Also SlateDB, a recently open-sourced embedded database built on object storage just moved to Commonhaus, which goes to show that the foundation also is a great home for young projects, relatively early in their lifecycle.
As such, I think moving to Commonhaus is an outstanding milestone for the Debezium project, ensuring its ongoing success in the future. Big kudos to the Debezium team for making this move, and massive props to Red Hat for supporting this step. It shows a deep understanding of and belief into open-source and its unique advantages, not paralleled by many other organizations. Now, some folks might wonder whether this is about dumping a project to an open-source foundation and then quickly pulling resources after that. Needless to say that I am not a spokesperson for Red Hat and I can’t predict what’s going to happen in the future. But personally, this is not something I am worried about. Historically, this isn’t something the company has been doing (with the exception of the Ceylon programming language perhaps, which got discontinued pretty quickly after moving to the Eclipse Foundation). Case in point, they just published a job posting for a Principal Software Engineer working on Debezium.
To wrap things up, I think the future is looking really bright for Debezium. The need for CDC and the interest in Debezium as the leading open-source implementation is unbroken. At the same time, it’s a very active space, with new projects popping up frequently, so it’s vital for Debezium and its community to keep moving and innovating. The move to Commonhaus lays an excellent foundation for this next chapter of Debezium’s success. With the team currently discussing the project roadmap for 2025, it’s a perfect time for getting involved and becoming a part of the journey.