DBMS > Atos Standard Common Repository vs. Datomic vs. DolphinDB vs. Newts

System Properties Comparison Atos Standard Common Repository vs. Datomic vs. DolphinDB vs. Newts

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

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

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

Time Series DBMS based on Cassandra

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.13
Rank	#80	Overall
	#6	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

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

www.datomic.com

www.dolphindb.com

opennms.github.io/newts

Technical documentation

docs.datomic.com

docs.dolphindb.cn/en/help200/index.html

github.com/OpenNMS/newts/wiki

Developer

Atos Convergence Creators

Cognitect

DolphinDB, Inc

OpenNMS Group

Initial release

2016

2012

2018

2014

Current release

1703

1.0.6735, June 2023

v2.00.4, January 2022

License

Commercial or Open Source

commercial

limited edition free

commercial

free community version available

Open Source

Apache 2.0

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

C++

Java

Server operating systems

Linux

All OS with a Java VM

Linux
Windows

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

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

SQL

Support of SQL

SQL-like query language

APIs and other access methods

LDAP

RESTful HTTP API

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

HTTP REST
Java API

Supported programming languages

All languages with LDAP bindings

Clojure
Java

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

Java

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Triggers

yes

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

But extensive use of caching in the application peers

horizontal partitioning

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

selectable replication factor

based on Cassandra

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

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

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

Administrators, Users, Groups

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

Share this page