DBMS > Atos Standard Common Repository vs. Drizzle vs. OrigoDB vs. STSdb vs. TigerGraph

System Properties Comparison Atos Standard Common Repository vs. Drizzle vs. OrigoDB vs. STSdb vs. TigerGraph

Editorial information provided by DB-Engines

Name

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

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A fully ACID in-memory object graph database

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Object oriented DBMS

Key-value store

Graph DBMS

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

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

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

origodb.com

github.com/STSSoft/STSdb4

www.tigergraph.com

Technical documentation

origodb.com/docs

docs.tigergraph.com

Developer

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

Robert Friberg et al

STS Soft SC

Initial release

2016

2008

2009

under the name LiveDB

2011

2017

Current release

1703

7.2.4, September 2012

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

GPLv2, commercial license available

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

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux
Windows

Windows

Linux

Data scheme

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

optional

yes

User defined using .NET types and collections

yes

primitive types and user defined types (classes)

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (GSQL)

APIs and other access methods

LDAP

JDBC

.NET Client API
HTTP API
LINQ

.NET Client API

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

C
C++
Java
PHP

.Net

C#
Java

C++
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication

none

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

Foreign keys

Referential integrity

yes

depending on model

yes

Relationships in graphs

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

Write ahead log

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Role based authorization

Role-based access control

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

TigerGraph Unveils CoPilot, Version 4.0, and New CEO
30 April 2024, Datanami

How TigerGraph CoPilot enables graph-augmented AI
30 April 2024, InfoWorld

TigerGraph unveils GenAI assistant, introduces new CEO
30 April 2024, TechTarget

TigerGraph Bolsters DB for Enterprise Graph Workloads
1 November 2023, Datanami

Aerospike takes on Neo4j and TigerGraph with launch of graph database
20 June 2023, SiliconANGLE News

provided by Google News

Share this page