DBMS > Atos Standard Common Repository vs. RocksDB vs. SAP SQL Anywhere vs. Splunk vs. STSdb

System Properties Comparison Atos Standard Common Repository vs. RocksDB vs. SAP SQL Anywhere vs. Splunk vs. STSdb

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

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Analytics Platform for Big Data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Key-value store

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

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

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

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

www.splunk.com

github.com/STSSoft/STSdb4

Technical documentation

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

docs.splunk.com/Documentation/Splunk

Developer

Atos Convergence Creators

Facebook, Inc.

SAP

formerly Sybase

Splunk Inc.

STS Soft SC

Initial release

2016

2013

1992

2003

2011

Current release

1703

8.11.4, April 2024

17, July 2015

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Limited free edition and free developer edition available

Open Source

GPLv2, commercial license 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

Java

C++

Server operating systems

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

primitive types and user defined types (classes)

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

APIs and other access methods

LDAP

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

.NET Client API

Supported programming languages

All languages with LDAP bindings

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

yes, in C/C++, Java, .Net or Perl

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Database mirroring

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

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

ACID

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

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.