DBMS > Atos Standard Common Repository vs. Galaxybase vs. InfinityDB vs. Infobright

System Properties Comparison Atos Standard Common Repository vs. Galaxybase vs. InfinityDB vs. Infobright

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.

Description

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

Scalable, ACID-compliant native distributed parallel graph platform

A Java embedded Key-Value Store which extends the Java Map interface

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Primary database model

Document store
Key-value store

Graph DBMS

Key-value store

Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Website

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

galaxybase.com

boilerbay.com

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

boilerbay.com/infinitydb/manual

Developer

Atos Convergence Creators

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Boiler Bay Inc.

Ignite Technologies Inc.; formerly InfoBright Inc.

Initial release

2016

2017

2002

2005

Current release

1703

Nov 20, November 2021

4.0

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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 and Java

Java

Server operating systems

Linux

All OS with a Java VM

Linux
Windows

Data scheme

Schema and schema-less with LDAP views

Strong typed schema

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

Typing

predefined data types such as float or date

optional

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

Knowledge Grid Technology used instead

SQL

Support of SQL

yes

APIs and other access methods

LDAP

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

ADO.NET
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Go
Java
Python

Java

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined procedures and functions

Triggers

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

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

manual creation possible, using inversions based on multi-value capability

Transaction concepts

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

Atomic execution of specific operations

ACID

Optimistic locking for transactions; no isolation for bulk loads

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

User concepts

Access control

LDAP bind authentication

Role-based access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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

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

provided by Google News

Share this page