DBMS > Atos Standard Common Repository vs. GridGain vs. OpenTSDB vs. Tkrzw vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. GridGain vs. OpenTSDB 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

GridGain is an in-memory computing platform, built on Apache Ignite

Scalable Time Series DBMS based on HBase

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

Key-value store
Relational DBMS

Time Series DBMS

Key-value store

Relational DBMS

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

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

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

Website

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

www.gridgain.com

opentsdb.net

dbmx.net/tkrzw

yaacomo.com

Technical documentation

www.gridgain.com/docs/index.html

opentsdb.net/docs/build/html/index.html

Developer

Atos Convergence Creators

GridGain Systems, Inc.

currently maintained by Yahoo and other contributors

Mikio Hirabayashi

Q2WEB GmbH

Initial release

2016

2007

2011

2020

2009

Current release

1703

GridGain 8.5.1

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

LGPL

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

Java, C++, .Net

Java

C++

Server operating systems

Linux

Linux
OS X
Solaris
Windows

Linux
Windows

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

numeric data for metrics, strings for tags

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

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

LDAP

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP API
Telnet API

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C#
C++
Java
PHP
Python
Ruby
Scala

Erlang
Go
Java
Python
R
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

based on HBase

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

selectable replication factor

based on HBase

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

based on HBase

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

ACID

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

using specific database classes

yes

User concepts

Access control

LDAP bind authentication

Security Hooks for custom implementations

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

Time Series DBMS are the database category with the fastest increase in popularity
4 July 2016, Matthias Gelbmann

show all

Recent citations in the news

GridGain in-memory data and generative AI – Blocks and Files
10 May 2024, Blocks & Files

GridGain to Sponsor and Speak at Three Key Industry Events in May 2024
6 May 2024, Martechcube

GridGain's 2023 Growth Positions Company for Strong 2024
25 January 2024, Datanami

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Adds Andy Sacks as Chief Revenue Officer, Promotes Lalit Ahuja to Chief Customer and Product Officer ...
17 July 2023, Yahoo Finance

provided by Google News

Comparing Different Time-Series Databases
10 February 2022, hackernoon.com

Brain Monitoring with Kafka, OpenTSDB, and Grafana
5 August 2016, KDnuggets

MapR to help admins peer into dense Hadoop clusters
28 June 2016, SiliconANGLE News

Comparing InfluxDB, TimescaleDB, and QuestDB Timeseries Databases
30 June 2021, Towards Data Science

A real-time processing revival – O'Reilly
1 April 2015, oreilly.com

provided by Google News

Share this page