DBMS > Atos Standard Common Repository vs. Splunk vs. TerminusDB vs. Tkrzw vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. Splunk vs. TerminusDB vs. Tkrzw vs. Yaacomo

Editorial information provided by DB-Engines

Name

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

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

Analytics Platform for Big Data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Secondary database models

Document store
RDF store

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

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

www.splunk.com

terminusdb.com

dbmx.net/tkrzw

yaacomo.com

Technical documentation

docs.splunk.com/Documentation/Splunk

terminusdb.github.io/terminusdb/#

Developer

Atos Convergence Creators

Splunk Inc.

DataChemist Ltd.

Mikio Hirabayashi

Q2WEB GmbH

Initial release

2016

2003

2018

2020

2009

Current release

1703

11.0.0, January 2023

0.9.3, August 2020

License

Commercial or Open Source

commercial

Limited free edition and free developer edition available

Open Source

GPL V3

Open Source

Apache Version 2.0

commercial

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

Prolog, Rust

C++

Server operating systems

Linux

Linux
OS X
Solaris
Windows

Linux

Linux
macOS

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

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

Splunk Search Processing Language for search commands

SQL-like query language (WOQL)

yes

APIs and other access methods

LDAP

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C#
Java
JavaScript
PHP
Python
Ruby

JavaScript
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Graph Partitioning

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Journaling Streams

none

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using specific database classes

yes

User concepts

Access control

LDAP bind authentication

Access rights for users and roles

Role-based access control

fine grained access rights according to SQL-standard

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

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

How TerminusDB is commercializing its open source graph database
16 March 2021, VentureBeat

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Dublin-based data collaboration tool TerminusDB raises €3.6 million in seed round
15 March 2021, Tech.eu

[MCR2030-CAMS-ARISE-UNDRR Webinar] Preventing cascading failures of critical assets: Using the Open-Source ...
12 April 2022, United Nations Office for Disaster Risk Reduction

Trinity College spinout TerminusDB secures €3.6m in investment
15 March 2021, The Irish Times

provided by Google News

Share this page