DBMS > Atos Standard Common Repository vs. Infobright vs. OrientDB vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. Infobright vs. OrientDB vs. Yaacomo

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.

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

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

Multi-model DBMS (Document, Graph, Key/Value)

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

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

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

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	3.27
Rank	#97	Overall
	#16	Document stores
	#6	Graph DBMS
	#15	Key-value stores

Website

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

ignitetech.com/softwarelibrary/infobrightdb

orientdb.org

yaacomo.com

Technical documentation

www.orientdb.com/docs/last/index.html

Developer

Atos Convergence Creators

Ignite Technologies Inc.; formerly InfoBright Inc.

OrientDB LTD; CallidusCloud; SAP

Q2WEB GmbH

Initial release

2016

2005

2010

2009

Current release

1703

3.2.29, March 2024

License

Commercial or Open Source

commercial

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

Open Source

Apache version 2

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

Server operating systems

Linux

Linux
Windows

All OS with a Java JDK (>= JDK 6)

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

SQL-like query language, no joins

yes

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

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

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

Java, Javascript

Triggers

yes

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

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

relationship in graphs

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

User concepts

Access control

LDAP bind authentication

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Access rights for users and roles; record level security configurable

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

Graph DBMS increased their popularity by 500% within the last 2 years
3 March 2015, Paul Andlinger

Graph DBMSs are gaining in popularity faster than any other database category
21 January 2014, Matthias Gelbmann

show all

Recent citations in the news

The 12 Best Graph Databases to Consider for 2024
22 October 2023, Solutions Review

OrientDB: A Flexible and Scalable Multi-Model NoSQL DBMS
21 January 2022, Open Source For You

Comparing Graph Databases II. Part 2: ArangoDB, OrientDB, and… | by Sam Bell
20 September 2019, Towards Data Science

CallidusCloud Acquires Leading Multi-Model Database Technology
19 September 2017, GlobeNewswire

K2View updates DataOps platform with data fabric automation
11 May 2021, TechTarget

provided by Google News

Share this page