DBMS > HEAVY.AI vs. MySQL vs. PostGIS vs. Rockset vs. SpatiaLite

System Properties Comparison HEAVY.AI vs. MySQL vs. PostGIS vs. Rockset vs. SpatiaLite

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

Spatial extension of PostgreSQL

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Spatial extension of SQLite

Primary database model

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Document store

Spatial DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

Relational DBMS

Relational DBMS
Search engine

Relational DBMS

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

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Score	1.07
Rank	#180	Overall
	#31	Document stores

Score	1.56
Rank	#142	Overall
	#3	Spatial DBMS

Website

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

www.mysql.com

postgis.net

rockset.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

docs.heavy.ai

dev.mysql.com/doc

postgis.net/documentation

docs.rockset.com

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

HEAVY.AI, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Rockset

Alessandro Furieri

Initial release

2016

1995

2005

2019

2008

Current release

5.10, January 2022

9.0.0, July 2024

3.4.2, February 2024

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++ and CUDA

C and C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

hosted

server-less

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

dynamic typing

yes

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

Read-only SQL queries, including JOINs

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

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

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

Access rights for users and organizations can be defined via Rockset console

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.