DBMS > Atos Standard Common Repository vs. Memcached vs. OrientDB vs. SQLite

System Properties Comparison Atos Standard Common Repository vs. Memcached vs. OrientDB vs. SQLite

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

In-memory key-value store, originally intended for caching

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

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Key-value store

Key-value store

Document store
Graph DBMS
Key-value store

Relational DBMS

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

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

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

www.memcached.org

orientdb.org

www.sqlite.org

Technical documentation

github.com/memcached/memcached/wiki

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

www.sqlite.org/docs.html

Developer

Atos Convergence Creators

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Initial release

2016

2003

2010

2000

Current release

1703

1.6.25, March 2024

3.2.29, March 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

Apache version 2

Open Source

Public Domain

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

FreeBSD
Linux
OS X
Unix
Windows

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

server-less

Data scheme

Schema and schema-less with LDAP views

schema-free

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

yes

dynamic column types

Typing

predefined data types such as float or date

optional

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

LDAP

Proprietary protocol

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication

none

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

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

via file-system locks

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

yes

using SASL (Simple Authentication and Security Layer) protocol

Access rights for users and roles; record level security configurable

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.