GitHub user jianlirong added a comment to the discussion: why incubating the 
greenplum database again?

Thanks for the question.

The motivation behind Apache Cloudberry comes from several observations about 
the evolution of the PostgreSQL ecosystem over the past few years.

First, Greenplum has accumulated many years of production experience and has 
been widely adopted across different industries. It also established itself as 
one of the most mature open-source MPP databases built on PostgreSQL. As the 
project evolved away from its previous open development model, we felt there 
was still a strong need in the community for a vendor-neutral, Apache-governed 
open-source successor that could continue serving users who value openness, 
long-term sustainability, and community-driven innovation.

Second, Apache HAWQ and Apache Cloudberry were created to solve very different 
problems. HAWQ was designed as a SQL-on-Hadoop engine, with its architecture 
tightly integrated with the Hadoop ecosystem and based on an older PostgreSQL 
codebase. Cloudberry, on the other hand, is a distributed MPP database designed 
for modern analytics workloads, while continuously evolving together with newer 
PostgreSQL releases. Although the projects share some historical roots, their 
technical goals and target use cases are fundamentally different.

Finally, the analytical database ecosystem has become much richer over the last 
decade. Excellent systems such as ClickHouse, Doris, and StarRocks have each 
established their own strengths and communities. At the same time, we continue 
to see strong demand for an open-source distributed database that combines:

1. close compatibility with modern PostgreSQL,
2. a proven shared-nothing MPP architecture,
3. rich SQL capabilities,
4. enterprise-grade stability and scalability, and
5. an open, community-governed development model.

Apache Cloudberry is our effort to meet that demand. Rather than replacing 
existing systems, we hope to provide another strong option for users and 
organizations whose requirements align with these goals.

Our goal is not to compete with any particular project, but to contribute 
another healthy and sustainable choice to the open-source ecosystem. We believe 
that diversity, open governance, and collaboration ultimately benefit both 
users and the PostgreSQL community as a whole.

Lirong

GitHub link: 
https://github.com/apache/cloudberry/discussions/1877#discussioncomment-17861290

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to