DBMS > EJDB vs. IBM Db2 warehouse vs. MySQL vs. Splunk

System Properties Comparison EJDB vs. IBM Db2 warehouse vs. MySQL vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Cloud-based data warehousing service

Widely used open source RDBMS

Analytics Platform for Big Data

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	1.26
Rank	#162	Overall
	#73	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Website

github.com/Softmotions/ejdb

www.ibm.com/products/db2/warehouse

www.mysql.com

www.splunk.com

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

dev.mysql.com/doc

docs.splunk.com/Documentation/Splunk

Developer

Softmotions

IBM

Oracle

since 2010, originally MySQL AB, then Sun

Splunk Inc.

Initial release

2012

2014

1995

2003

Current release

9.0.0, July 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Server operating systems

server-less

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

Splunk Search Processing Language for search commands

APIs and other access methods

in-process shared library

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

PL/SQL, SQL PL

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

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

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.