DBMS > EJDB vs. IBM Db2 vs. Splunk vs. SQLite

System Properties Comparison EJDB vs. IBM Db2 vs. Splunk vs. SQLite

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)

Common in IBM host environments, 2 different versions for host and Windows/Linux

Analytics Platform for Big Data

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Search engine

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/Softmotions/ejdb

www.ibm.com/products/db2

www.splunk.com

www.sqlite.org

Technical documentation

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

www.ibm.com/docs/en/db2

docs.splunk.com/Documentation/Splunk

www.sqlite.org/docs.html

Developer

Softmotions

IBM

Splunk Inc.

Dwayne Richard Hipp

Initial release

2012

1983

host version

2003

2000

Current release

12.1, October 2016

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

free version is available

commercial

Limited free edition and free developer edition available

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

Server operating systems

server-less

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
OS X
Solaris
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

yes

SQL-92 is not fully supported

APIs and other access methods

in-process shared library

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C#
Java
JavaScript
PHP
Python
Ruby

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

only with Windows/Unix/Linux Version

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

with separate tools (MQ, InfoSphere)

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

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

Read/Write Locking

yes

via file-system locks

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

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.