DBMS > Oracle vs. Splunk vs. Tkrzw vs. XTDB

System Properties Comparison Oracle vs. Splunk vs. Tkrzw vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS

Analytics Platform for Big Data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

A general purpose database with bitemporal SQL and Datalog and graph queries

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	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

www.oracle.com/database

www.splunk.com

dbmx.net/tkrzw

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.oracle.com/en/database

docs.splunk.com/Documentation/Splunk

www.xtdb.com/docs

Developer

Oracle

Splunk Inc.

Mikio Hirabayashi

Juxt Ltd.

Initial release

1980

2003

2020

2019

Current release

23c, September 2023

0.9.3, August 2020

1.19, September 2021

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Limited free edition and free developer edition available

Open Source

Apache Version 2.0

Open Source

MIT License

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

Clojure

Server operating systems

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

Linux
OS X
Solaris
Windows

Linux
macOS

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

Schemaless in JSON and XML columns

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

Splunk Search Processing Language for search commands

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST

HTTP REST
JDBC

Supported programming languages

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

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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'

yes

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

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.