DBMS > EJDB vs. ReductStore vs. Splunk

System Properties Comparison EJDB vs. ReductStore 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)

Designed to manage unstructured time-series data efficiently, providing unique features such as storing time-stamped blobs with labels, customizable data retention policies, and a straightforward FIFO quota system.

Analytics Platform for Big Data

Primary database model

Document store

Time Series DBMS

Search engine

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Website

github.com/Softmotions/ejdb

github.com/reductstore
www.reduct.store

www.splunk.com

Technical documentation

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

www.reduct.store/docs

docs.splunk.com/Documentation/Splunk

Developer

Softmotions

ReductStore LLC

Splunk Inc.

Initial release

2012

2023

2003

Current release

1.9, March 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Business Source License 1.1

commercial

Limited free edition and free developer edition available

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

Server operating systems

server-less

Docker
Linux
macOS
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.

yes

Secondary indexes

yes

SQL

Support of SQL

Splunk Search Processing Language for search commands

APIs and other access methods

in-process shared library

HTTP API

HTTP REST

Supported programming languages

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

C++
JavaScript (Node.js)
Python
Rust

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

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

Transaction concepts

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

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

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.

User concepts

Access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Share this page