DBMS > 4D vs. Atos Standard Common Repository vs. JanusGraph vs. OrientDB vs. SQLite

System Properties Comparison 4D vs. Atos Standard Common Repository vs. JanusGraph vs. OrientDB vs. SQLite

Editorial information provided by DB-Engines

Name

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

Description

Application development environment with integrated database management system

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Document store
Key-value store

Graph DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

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

www.4d.com

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

janusgraph.org

orientdb.org

www.sqlite.org

Technical documentation

developer.4d.com

docs.janusgraph.org

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

www.sqlite.org/docs.html

Developer

4D, Inc

Atos Convergence Creators

Linux Foundation; originally developed as Titan by Aurelius

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Initial release

1984

2016

2017

2010

2000

Current release

v20, April 2023

1703

0.6.3, February 2023

3.2.29, March 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

OS X
Windows

Linux

Linux
OS X
Unix
Windows

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

server-less

Data scheme

yes

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

dynamic column types

Typing

predefined data types such as float or date

yes

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

yes

close to SQL 92

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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

4D proprietary IDE
PHP

All languages with LDAP bindings

Clojure
Java
Python

.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

yes

Java, Javascript

Triggers

yes

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

relationship in graphs

yes

Transaction concepts

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

ACID

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

Users and groups

LDAP bind authentication

User authentification and security via Rexster Graph Server

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.