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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	7.71
Rank	#46	Overall
	#29	Relational DBMS

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

greenplum.org

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

www.singlestore.com

www.sqlite.org

Technical documentation

docs.greenplum.org

docs.heavy.ai

docs.singlestore.com

www.sqlite.org/docs.html

Developer

Pivotal Software Inc.

HEAVY.AI, Inc.

SingleStore Inc.

Dwayne Richard Hipp

Initial release

2005

2016

2013

2000

Current release

7.0.0, September 2023

5.10, January 2022

8.5, January 2024

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; enterprise edition available

commercial

free developer 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++ and CUDA

C++, Go

Server operating systems

Linux

64 bit version required

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

but no triggers and foreign keys

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Thrift
Vega

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
Java
Perl
Python
R

All languages supporting JDBC/ODBC/Thrift
Python

Bash
C
C#
Java
JavaScript (Node.js)
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

Sharding

Round robin

Sharding

hash partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

Source-replica replication

stores two copies of each physical data partition on two separate nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can define user-defined aggregate functions for map-reduce-style calculations

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

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

Fine grained access control via users, groups and roles

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.