DBMS > EJDB vs. IBM Cloudant vs. Percona Server for MongoDB vs. Splunk

System Properties Comparison EJDB vs. IBM Cloudant vs. Percona Server for MongoDB 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)

Database as a Service offering based on Apache CouchDB

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Analytics Platform for Big Data

Primary database model

Document store

Search engine

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

github.com/Softmotions/ejdb

www.ibm.com/products/cloudant

www.percona.com/mongodb/software/percona-server-for-mongodb

www.splunk.com

Technical documentation

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

cloud.ibm.com/docs/Cloudant

docs.percona.com/percona-distribution-for-mongodb

docs.splunk.com/Documentation/Splunk

Developer

Softmotions

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Percona

Splunk Inc.

Initial release

2012

2010

2015

2003

Current release

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

GPL Version 2

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

Erlang

C++

Server operating systems

server-less

hosted

Linux

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

RESTful HTTP/JSON API

proprietary protocol using JSON

HTTP REST

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

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
Source-replica 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

Eventual Consistency

Eventual Consistency
Immediate Consistency

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

atomic operations within a document possible

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

Optimistic 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.

yes

via In-Memory Engine

User concepts

Access control

Access rights for users can be defined per database

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

Recent citations in the news

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, ibm.com

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, ibm.com

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

5 Reasons to Run MongoDB on Kubernetes
6 March 2024, The New Stack

Percona launches management system aimed at open-source databases
17 May 2022, The Register

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

The essential guide to MongoDB security
2 February 2017, InfoWorld

The Case Against the Server Side Public License (SSPL)
11 October 2022, The New Stack

provided by Google News

Share this page