DBMS > IBM Db2 Event Store vs. Newts vs. Quasardb vs. SQLite vs. VoltDB

System Properties Comparison IBM Db2 Event Store vs. Newts vs. Quasardb vs. SQLite vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Distributed Event Store optimized for Internet of Things use cases

Time Series DBMS based on Cassandra

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Event Store
Time Series DBMS

Time Series DBMS

Relational DBMS

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

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.ibm.com/products/db2-event-store

opennms.github.io/newts

quasar.ai

www.sqlite.org

www.voltdb.com

Technical documentation

www.ibm.com/docs/en/db2-event-store

github.com/OpenNMS/newts/wiki

doc.quasar.ai/master

www.sqlite.org/docs.html

docs.voltdb.com

Developer

IBM

OpenNMS Group

quasardb

Dwayne Richard Hipp

VoltDB Inc.

Initial release

2017

2014

2009

2000

2010

Current release

2.0

3.14.1, January 2024

3.46.0 (23 May 2024), May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

free developer edition available

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Public Domain

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java

C++

Java, C++

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

Linux
OS X
Windows

BSD
Linux
OS X
Windows

server-less

Linux
OS X

for development

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

integer and binary

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.

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

SQL-like query language

yes

SQL-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

HTTP REST
Java API

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

Java

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

consistent hashing

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

selectable replication factor

based on Cassandra

Source-replica replication with selectable replication factor

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

No - written data is immutable

yes

via file-system locks

yes

Data access is serialized by the server

Durability

Support for making data persistent

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

by using LevelDB

yes

Snapshots and command logging

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

Users and roles with access to stored procedures

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.