DBMS > Atos Standard Common Repository vs. Dragonfly vs. Snowflake vs. TempoIQ vs. Valentina Server

System Properties Comparison Atos Standard Common Repository vs. Dragonfly vs. Snowflake vs. TempoIQ vs. Valentina Server

Editorial information provided by DB-Engines

Name

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

TempoIQ seems to be decommissioned. It 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

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

Cloud-based data warehousing service for structured and semi-structured data

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Object-relational database and reports server

Primary database model

Document store
Key-value store

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

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

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

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

www.snowflake.com

tempoiq.com (offline)

www.valentina-db.net

Technical documentation

www.dragonflydb.io/docs

docs.snowflake.net/manuals/index.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Atos Convergence Creators

DragonflyDB team and community contributors

Snowflake Computing Inc.

TempoIQ

Paradigma Software

Initial release

2016

2023

2014

2012

1999

Current release

1703

1.0, March 2023

5.7.5

License

Commercial or Open Source

commercial

Open Source

BSL 1.1

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

Linux

hosted

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

scheme-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

APIs and other access methods

LDAP

Proprietary protocol

RESP - REdis Serialization Protocol

CLI Client
JDBC
ODBC

HTTP API

ODBC

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 (Node.js)
Python

C#
Java
JavaScript

Node.js
Python
Ruby

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

Lua

user defined functions

yes

Triggers

yes

publish/subscribe channels provide some trigger functionality

similar concept for controling cloud resources

yes

Realtime Alerts

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

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

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

Users with fine-grained authorization concept, user roles and pluggable authentication

simple authentication-based access control

fine grained access rights according to SQL-standard

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.