DBMS > Atos Standard Common Repository vs. Dragonfly vs. FatDB vs. TerminusDB

System Properties Comparison Atos Standard Common Repository vs. Dragonfly vs. FatDB vs. TerminusDB

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

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Key-value store

Key-value store

Document store
Key-value store

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

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

github.com/dragonflydb/dragonfly
www.dragonflydb.io

terminusdb.com

Technical documentation

www.dragonflydb.io/docs

terminusdb.github.io/terminusdb/#

Developer

Atos Convergence Creators

DragonflyDB team and community contributors

FatCloud

DataChemist Ltd.

Initial release

2016

2023

2012

2018

Current release

1703

1.0, March 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

BSL 1.1

commercial

Open Source

GPL V3

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++

Prolog, Rust

Server operating systems

Linux

Windows

Linux

Data scheme

Schema and schema-less with LDAP views

scheme-free

schema-free

yes

Typing

predefined data types such as float or date

optional

strings, hashes, lists, sets, sorted sets, bit arrays

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

Via inetgration in SQL Server

SQL-like query language (WOQL)

APIs and other access methods

LDAP

Proprietary protocol

RESP - REdis Serialization Protocol

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

JavaScript
Python

Server-side scripts

Stored procedures

Lua

yes

via applications

yes

Triggers

yes

publish/subscribe channels provide some trigger functionality

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

selectable replication factor

Journaling Streams

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

Eventual 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

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

Password-based authentication

Can implement custom security layer via applications

Role-based access control

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

DragonflyDB Announces $21m in New Funding and General Availability
21 March 2023, Business Wire

DragonflyDB reels in $21M for its speedy in-memory database
21 March 2023, SiliconANGLE News

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Intel Linux Kernel Optimizations Show Huge Benefit For High Core Count Servers
29 March 2023, Phoronix

SFU Computing Science researchers receive 2022 ACM SIGMOD Research Highlight Award.
24 February 2023, Simon Fraser University News

provided by Google News

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

Trinity College spinout TerminusDB secures €3.6m in investment
15 March 2021, The Irish Times

[MCR2030-CAMS-ARISE-UNDRR Webinar] Preventing cascading failures of critical assets: Using the Open-Source ...
12 April 2022, United Nations Office for Disaster Risk Reduction

Irish start-ups received €28m from Enterprise Ireland in 2021
7 April 2022, SiliconRepublic.com

Bus Terminus Update - April 26th
26 April 2021, Around DB and Life on Lantau

provided by Google News

Share this page