A · leads
DuckDB
95.5
43,126 stars · MIT
Databases
DuckDB leads by 19.1 · decisive
A · leads
95.5
43,126 stars · MIT
B
76.4
38,316 stars · license n/a
DuckDB versus interview is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in C++. The composite score is 95.5 for DuckDB and 76.4 for interview.
DuckDB has 43,126 GitHub stars to interview's 38,316, a gap of 4,810 (1.13×). Forks are 4,214 for DuckDB and 8,056 for interview. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 93 versus 100.
Push history: DuckDB was last pushed on 17 November 2026 (0 days ago), and interview was last pushed on 17 September 2026 (61 days ago). Open issues stand at 1,261 for DuckDB (0.029 per star) and 3 for interview (0.000 per star). Issue-health scores are 70 and 96; activity scores are 100 and 58.
DuckDB is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. interview is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for DuckDB and 30 for interview. This is a procurement signal, not legal advice.
Only DuckDB is marked self-hostable here (43,126 stars, deploy score 100). interview is not (38,316 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: DuckDB is open source, interview is unpriced in this catalog.
The lead is split. DuckDB is furthest ahead on license flexibility (96 to 30), while interview is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
DuckDB finishes ahead at 95.5 against interview at 76.4, a 19.1 point decisive margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | DuckDB | interview |
|---|---|---|
| GitHub stars | 43,126 | 38,316 |
| Forks | 4,214 | 8,056 |
| Open issues | 1,261 | 3 |
| Adoption | 100 | 99 |
| Activity | 100 | 58 |
| Community | 93 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 95.5 | 76.4 |
DuckDB is an in-process analytical database, often described as SQLite for OLAP. It runs inside the application process and queries local files such as Parquet.
📚 C/C++ 技术面试基础知识总结,包括语言、程序库、数据结构、算法、系统、网络、链接装载库等知识及面试经验、招聘、内推等信息。This repository is a summary of the basic knowledge of recruiting job seekers and beginners in the direction of C/C++ technology, including language, program library, data structure, algorithm, system, network, link loading library, interview experience, recruitment, recommendation, etc.
DuckDB has more GitHub stars: 43,126 versus 38,316 for interview. The gap is 4,810 stars.
DuckDB was pushed more recently: 17 November 2026 versus 17 September 2026 for interview. That is 61 days apart.
Only DuckDB is marked self-hostable. interview is not.
DuckDB is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. interview is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
DuckDB scores 95.5 and interview scores 76.4. This page calls that a decisive lead for DuckDB.