DBMS > Hazelcast vs. NuoDB vs. SQLite vs. ToroDB

System Properties Comparison Hazelcast vs. NuoDB vs. SQLite vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

A widely adopted in-memory data grid

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Widely used embeddable, in-process RDBMS

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

Primary database model

Key-value store

Relational DBMS

Document store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.89
Rank	#198	Overall
	#92	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

hazelcast.com

www.3ds.com/nuodb-distributed-sql-database

www.sqlite.org

github.com/torodb/server

Technical documentation

hazelcast.org/imdg/docs

doc.nuodb.com

www.sqlite.org/docs.html

Developer

Hazelcast

Dassault Systèmes

originally NuoDB, Inc.

Dwayne Richard Hipp

8Kdata

Initial release

2008

2013

2000

2016

Current release

5.3.6, November 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

limited edition free

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

Java

C++

Java

Server operating systems

All OS with a Java VM

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

server-less

All OS with a Java 7 VM

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
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

Event Listeners, Executor Services

Java, SQL

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

data is dynamically stored/cached on the nodes where it is read/written

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

Managed transparently by NuoDB

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

ACID

tunable commit protocol

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Temporary table

yes

User concepts

Access control

Role-based access control

Standard SQL roles/ privileges, Administrative Users

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.