DBMS > IBM Db2 Event Store vs. Kinetica vs. RDF4J vs. SQLite

System Properties Comparison IBM Db2 Event Store vs. Kinetica vs. RDF4J vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Event Store optimized for Internet of Things use cases

Fully vectorized database across both GPUs and CPUs

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Widely used embeddable, in-process RDBMS

Primary database model

Event Store
Time Series DBMS

Relational DBMS

RDF store

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.18
Rank	#315	Overall
	#2	Event Stores
	#26	Time Series DBMS

Score	0.42
Rank	#261	Overall
	#120	Relational DBMS

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

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

www.kinetica.com

rdf4j.org

www.sqlite.org

Technical documentation

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

docs.kinetica.com

rdf4j.org/documentation

www.sqlite.org/docs.html

Developer

IBM

Kinetica

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Dwayne Richard Hipp

Initial release

2017

2012

2004

2000

Current release

2.0

7.1, August 2021

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

free developer edition available

commercial

Open Source

Eclipse Distribution License (EDL), v1.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 and C++

C, C++

Java

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

Linux

Linux
OS X
Unix
Windows

server-less

Data scheme

yes

RDF Schemas

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

through the embedded Spark runtime

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C++
Java
JavaScript (Node.js)
Python

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

user defined functions

yes

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

No - written data is immutable

yes

via file-system locks

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

in-memory storage is supported as well

yes

In-memory capabilities

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

yes

GPU vRAM or System RAM

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

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.