DBMS > Graph Engine vs. Graphite vs. HEAVY.AI vs. SQLite vs. ToroDB

System Properties Comparison Graph Engine vs. Graphite vs. HEAVY.AI vs. SQLite vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Graph DBMS
Key-value store

Time Series DBMS

Relational DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.graphengine.io

github.com/graphite-project/graphite-web

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

www.sqlite.org

github.com/torodb/server

Technical documentation

www.graphengine.io/docs/manual

graphite.readthedocs.io

docs.heavy.ai

www.sqlite.org/docs.html

Developer

Microsoft

Chris Davis

HEAVY.AI, Inc.

Dwayne Richard Hipp

8Kdata

Initial release

2010

2006

2016

2000

2016

Current release

5.10, January 2022

3.45.3 (15 April 2024), April 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

Open Source

AGPL-V3

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

.NET and C

Python

C++ and CUDA

Java

Server operating systems

.NET

Linux
Unix

Linux

server-less

All OS with a Java 7 VM

Data scheme

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

yes

string, integer, double, boolean, date, object_id

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

HTTP API
Sockets

JDBC
ODBC
Thrift
Vega

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
F#
Visual Basic

JavaScript (Node.js)
Python

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

horizontal partitioning

none

Sharding

Round robin

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
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

locking

yes

via file-system locks

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Access rights for users 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.