DBMS > Atos Standard Common Repository vs. Axibase vs. Coveo vs. RocksDB vs. Splunk

System Properties Comparison Atos Standard Common Repository vs. Axibase vs. Coveo vs. RocksDB vs. Splunk

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Analytics Platform for Big Data

Primary database model

Document store
Key-value store

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

axibase.com/docs/atsd/finance

www.coveo.com

rocksdb.org

www.splunk.com

Technical documentation

docs.coveo.com

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Atos Convergence Creators

Axibase Corporation

Coveo

Facebook, Inc.

Splunk Inc.

Initial release

2016

2013

2012

2013

2003

Current release

1703

15585

9.2.1, May 2024

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

Open Source

BSD

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

Java

C++

Server operating systems

Linux

hosted

Linux

Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

short, integer, long, float, double, decimal, string

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

SQL-like query language

Splunk Search Processing Language for search commands

APIs and other access methods

LDAP

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

RESTful HTTP API

C++ API
Java API

HTTP REST

Supported programming languages

All languages with LDAP bindings

Go
Java
PHP
Python
R
Ruby

C#
Java
JavaScript
Python

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

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 or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

yes

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

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

LDAP bind authentication

granular access controls, API key management, content filters

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.