DBMS > DuckDB vs. Greenplum vs. HEAVY.AI vs. SQLite

System Properties Comparison DuckDB vs. Greenplum vs. HEAVY.AI vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, in-process, column-oriented SQL OLAP RDBMS

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	5.61
Rank	#60	Overall
	#34	Relational DBMS

Score	7.71
Rank	#46	Overall
	#29	Relational DBMS

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

duckdb.org

greenplum.org

github.com/heavyai/heavydb
www.heavy.ai

www.sqlite.org

Technical documentation

duckdb.org/docs

docs.greenplum.org

docs.heavy.ai

www.sqlite.org/docs.html

Developer

Pivotal Software Inc.

HEAVY.AI, Inc.

Dwayne Richard Hipp

Initial release

2018

2005

2016

2000

Current release

1.0.0, June 2024

7.0.0, September 2023

5.10, January 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Apache Version 2; enterprise edition available

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C++ and CUDA

Server operating systems

server-less

Linux

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

since Version 4.2

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

JDBC
ODBC

JDBC
ODBC
Thrift
Vega

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

C
Java
Perl
Python
R

All languages supporting JDBC/ODBC/Thrift
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.