DBMS > GridDB vs. IBM Db2 vs. JanusGraph vs. SQLite

System Properties Comparison GridDB vs. IBM Db2 vs. JanusGraph vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable in-memory time series database optimized for IoT and Big Data

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Relational DBMS

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

Graph DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	123.05
Rank	#9	Overall
	#6	Relational DBMS

Score	1.85
Rank	#134	Overall
	#12	Graph DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

griddb.net

www.ibm.com/products/db2

janusgraph.org

www.sqlite.org

Technical documentation

docs.griddb.net

www.ibm.com/docs/en/db2

docs.janusgraph.org

www.sqlite.org/docs.html

Developer

Toshiba Corporation

IBM

Linux Foundation; originally developed as Titan by Aurelius

Dwayne Richard Hipp

Initial release

2013

1983

host version

2017

2000

Current release

5.1, August 2022

12.1, October 2016

1.0.0, October 2023

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

free version is available

Open Source

Apache 2.0

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 C++

Java

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
OS X
Unix
Windows

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL92, SQL-like TQL (Toshiba Query Language)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

Clojure
Java
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

only with Windows/Unix/Linux Version

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

with separate tools (MQ, InfoSphere)

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

User authentification and security via Rexster Graph Server

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.