DBMS > Graph Engine vs. HyperSQL vs. IBM Cloudant vs. SQL.JS vs. SQLite

System Properties Comparison Graph Engine vs. HyperSQL vs. IBM Cloudant vs. SQL.JS vs. SQLite

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

Database as a Service offering based on Apache CouchDB

Port of SQLite to JavaScript

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Document store

Relational 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	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.53
Rank	#252	Overall
	#116	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.graphengine.io

hsqldb.org

www.ibm.com/products/cloudant

sql.js.org

www.sqlite.org

Technical documentation

www.graphengine.io/docs/manual

hsqldb.org/web/hsqlDocsFrame.html

cloud.ibm.com/docs/Cloudant

sql.js.org/documentation/index.html

www.sqlite.org/docs.html

Developer

Microsoft

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Alon Zakai

enhancements implemented by others

Dwayne Richard Hipp

Initial release

2010

2001

2010

2012

2000

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

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

Erlang

JavaScript

Server operating systems

.NET

All OS with a Java VM

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

hosted

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

HTTP API

JDBC via HTTP
JDBC
ODBC

RESTful HTTP/JSON API

JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC
Java

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript

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

Java, SQL

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

except by serializing a db to a file

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 can be defined per database

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.