DBMS > Atos Standard Common Repository vs. Datomic vs. EJDB vs. mSQL vs. OrigoDB

System Properties Comparison Atos Standard Common Repository vs. Datomic vs. EJDB vs. mSQL vs. OrigoDB

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

Primary database model

Document store
Key-value store

Relational DBMS

Document store

Relational DBMS

Document store
Object oriented DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

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

Website

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

www.datomic.com

github.com/Softmotions/ejdb

hughestech.com.au/products/msql

origodb.com

Technical documentation

docs.datomic.com

github.com/Softmotions/ejdb/blob/master/README.md

origodb.com/docs

Developer

Atos Convergence Creators

Cognitect

Softmotions

Hughes Technologies

Robert Friberg et al

Initial release

2016

2012

1994

2009

under the name LiveDB

Current release

1703

1.0.6735, June 2023

4.4, October 2021

License

Commercial or Open Source

commercial

limited edition free

Open Source

GPLv2

commercial

free licenses can be provided

Open Source

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

Java, Clojure

Server operating systems

Linux

All OS with a Java VM

server-less

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

string, integer, double, bool, date, object_id

yes

User defined using .NET types and collections

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

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

LDAP

RESTful HTTP API

in-process shared library

JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages with LDAP bindings

Clojure
Java

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Triggers

yes

By using transaction functions

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

But extensive use of caching in the application peers

none

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

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

none

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

depending on model

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

Read/Write Locking

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

Write ahead log

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

LDAP bind authentication

Role based authorization

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

Stanchion Turns SQLite Into A Column Store
15 February 2024, iProgrammer

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Zoona Case Study
16 December 2017, AWS Blog

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

provided by Google News

Writing a Web Service in Perl
9 July 2003, PCQuest

Higher Education PS rules out ghost students before PAC
29 November 2018, diggers.news

provided by Google News

Share this page