DBMS > Atos Standard Common Repository vs. GridGain vs. SiriDB vs. Tkrzw vs. Transbase

System Properties Comparison Atos Standard Common Repository vs. GridGain vs. SiriDB vs. Tkrzw vs. Transbase

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

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

Open Source Time Series DBMS

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

A resource-optimized, high-performance, universally applicable RDBMS

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	0.00
Rank	#383	Overall
	#41	Time Series DBMS

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

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

www.gridgain.com

siridb.com

dbmx.net/tkrzw

www.transaction.de/en/products/transbase.html

Technical documentation

www.gridgain.com/docs/index.html

docs.siridb.com

www.transaction.de/en/products/transbase/features.html

Developer

Atos Convergence Creators

GridGain Systems, Inc.

Cesbit

Mikio Hirabayashi

Transaction Software GmbH

Initial release

2016

2007

2017

2020

1987

Current release

1703

GridGain 8.5.1

0.9.3, August 2020

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache Version 2.0

commercial

free development license

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

C++

C and C++

Server operating systems

Linux

Linux
OS X
Solaris
Windows

Linux

Linux
macOS

FreeBSD
Linux
macOS
Solaris
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

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages with LDAP bindings

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C++
Java
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

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

yes

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

yes

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

yes

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

User concepts

Access control

LDAP bind authentication

Security Hooks for custom implementations

simple rights management via user accounts

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

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 Named in the 2023 Gartner® Market Guide for Event Stream Processing
22 August 2023, GlobeNewswire

provided by Google News

SiriDB tijdreeks database analyseert time series data vanuit elke bron
22 January 2017, Dutch IT Channel

provided by Google News

Share this page