DBMS > Graph Engine vs. IBM Db2 vs. OpenTSDB vs. SQLite

System Properties Comparison Graph Engine vs. IBM Db2 vs. OpenTSDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Common in IBM host environments, 2 different versions for host and Windows/Linux

Scalable Time Series DBMS based on HBase

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Time Series DBMS

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.graphengine.io

www.ibm.com/products/db2

opentsdb.net

www.sqlite.org

Technical documentation

www.graphengine.io/docs/manual

www.ibm.com/docs/en/db2

opentsdb.net/docs/build/html/index.html

www.sqlite.org/docs.html

Developer

Microsoft

IBM

currently maintained by Yahoo and other contributors

Dwayne Richard Hipp

Initial release

2010

1983

host version

2011

2000

Current release

12.1, October 2016

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

free version is available

Open Source

LGPL

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

.NET and C

C and C++

Java

Server operating systems

.NET

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

HTTP API
Telnet API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
F#
Visual Basic

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

Erlang
Go
Java
Python
R
Ruby

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

Sharding

only with Windows/Unix/Linux Version

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

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

via file-system locks

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

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.