Learn how Apache Cloudberry and TimescaleDb differ in their key features, development activity, technology stack and community adoption, so you can decide which of these relational databases (sql) is best for you.
Last 30 days
Last commit
Repository age
Version
License
Repository

Last 30 days
Last commit
Repository age
Version
Repository

Both Apache Cloudberry and TimescaleDb have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
TimescaleDb significantly outpaces Apache Cloudberry in community adoption with 23,365 stars compared to 1,361 stars on GitHub. This 17.2x difference suggests TimescaleDb has a much larger and more active community. In terms of developer contributions, TimescaleDb has 1,138 forks, indicating strong developer engagement.
Apache Cloudberry is growing faster, adding 114 stars in the last 30 days (+9.1%) against adding 225 stars for TimescaleDb (+1%). Apache Cloudberry is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with Apache Cloudberry last updated 9 hours ago and TimescaleDb 7 hours ago.
Both tools share common technology foundations, being built with Bash, Python, C, Objective-C, Perl. However, they differ in their additional technology choices: Apache Cloudberry uses CSS, C++.
TimescaleDb has been in development longer, starting 9 years ago, compared to Apache Cloudberry which began 3 years ago. This 6.3-year head start suggests TimescaleDb may have more mature features and established processes.
Apache Cloudberry is licensed under Apache-2.0, while TimescaleDb's license terms are not publicly specified.
Both tools serve similar use cases in Relational Databases (SQL). However, they also have distinct specializations: Apache Cloudberry also focuses on Cloud Data Warehouses while TimescaleDb extends into Time Series Databases.