DBMS > Atos Standard Common Repository vs. DolphinDB vs. FatDB vs. Lovefield

System Properties Comparison Atos Standard Common Repository vs. DolphinDB vs. FatDB vs. Lovefield

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.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

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.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Document store
Key-value store

Time Series DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

Relational DBMS

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

Score	4.03
Rank	#78	Overall
	#6	Time Series DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Website

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

www.dolphindb.com

google.github.io/lovefield

Technical documentation

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

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Atos Convergence Creators

DolphinDB, Inc

FatCloud

Google

Initial release

2016

2018

2012

2014

Current release

1703

v2.00.4, January 2022

2.1.12, February 2017

License

Commercial or Open Source

commercial

free community version available

commercial

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

C++

JavaScript

Server operating systems

Linux

Linux
Windows

Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

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

Via inetgration in SQL Server

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

LDAP

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

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Supported programming languages

All languages with LDAP bindings

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

JavaScript

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

LDAP bind authentication

Administrators, Users, Groups

Can implement custom security layer via applications

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.

Share this page