DBMS > Atos Standard Common Repository vs. Drizzle vs. H2 vs. Splunk

System Properties Comparison Atos Standard Common Repository vs. Drizzle vs. H2 vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Analytics Platform for Big Data

Primary database model

Document store
Key-value store

Relational DBMS

Search engine

Secondary database models

Spatial DBMS

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

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

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

www.h2database.com

www.splunk.com

Technical documentation

www.h2database.com/html/main.html

docs.splunk.com/Documentation/Splunk

Developer

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

Thomas Mueller

Splunk Inc.

Initial release

2016

2008

2005

2003

Current release

1703

7.2.4, September 2012

2.2.220, July 2023

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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

Java

C++

Java

Server operating systems

Linux

FreeBSD
Linux
OS X

All OS with a Java VM

Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

optional

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

yes

with proprietary extensions

yes

Splunk Search Processing Language for search commands

APIs and other access methods

LDAP

JDBC

JDBC
ODBC

HTTP REST

Supported programming languages

All languages with LDAP bindings

C
C++
Java
PHP

Java

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

With clustering: 2 database servers on different computers operate on identical copies of a database

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

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

yes, multi-version concurrency control (MVCC)

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

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

show all

Share this page