DBMS > EsgynDB vs. KairosDB vs. Oracle vs. RDF4J

System Properties Comparison EsgynDB vs. KairosDB vs. Oracle vs. RDF4J

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Distributed Time Series DBMS based on Cassandra or H2

Widely used RDBMS

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

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	0.71
Rank	#230	Overall
	#20	Time Series DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Website

www.esgyn.cn

github.com/kairosdb/kairosdb

www.oracle.com/database

rdf4j.org

Technical documentation

kairosdb.github.io

docs.oracle.com/en/database

rdf4j.org/documentation

Developer

Esgyn

Oracle

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

Initial release

2015

2013

1980

2004

Current release

1.2.2, November 2018

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Eclipse Distribution License (EDL), v1.0.

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++, Java

Java

C and C++

Java

Server operating systems

Linux

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

yes

RDF Schemas

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

Graphite protocol
HTTP REST
Telnet API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Java
JavaScript

Node.js
PHP
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Java
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

In-memory capabilities

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

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

fine grained access rights according to SQL-standard

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.