DBMS > Graph Engine vs. HyperSQL vs. IBM Db2 warehouse vs. SQLite vs. TDSQL for MySQL

System Properties Comparison Graph Engine vs. HyperSQL vs. IBM Db2 warehouse vs. SQLite vs. TDSQL for MySQL

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Cloud-based data warehousing service

Widely used embeddable, in-process RDBMS

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Document store
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	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.85
Rank	#205	Overall
	#95	Relational DBMS

Website

www.graphengine.io

hsqldb.org

www.ibm.com/products/db2/warehouse

www.sqlite.org

www.tencentcloud.com/products/dcdb

Technical documentation

www.graphengine.io/docs/manual

hsqldb.org/web/hsqlDocsFrame.html

www.sqlite.org/docs.html

www.tencentcloud.com/document/product/1042

Developer

Microsoft

IBM

Dwayne Richard Hipp

Tencent

Initial release

2010

2001

2014

2000

2013

Current release

2.7.2, June 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

based on BSD license

commercial

Open Source

Public Domain

commercial

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

.NET and C

Java

Server operating systems

.NET

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

hosted

server-less

hosted

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Import/export of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

APIs and other access methods

RESTful HTTP API

HTTP API

JDBC via HTTP
JDBC
ODBC

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC

Supported programming languages

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC
Java

Java
JavaScript (Node.js)
Perl
PHP
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

C
C#
C++
Java
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Java, SQL

PL/SQL, SQL PL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

none

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

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

Users with fine-grained authorization concept

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.