DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. NSDb vs. OrigoDB vs. VictoriaMetrics

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. NSDb vs. OrigoDB vs. VictoriaMetrics

Editorial information provided by DB-Engines

Name

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

Description

Large scale data warehouse service for use with business intelligence tools

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fully ACID in-memory object graph database

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Relational DBMS

Document store
Key-value store

Time Series DBMS

Document store
Object oriented DBMS

Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Website

aws.amazon.com/redshift

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

nsdb.io

origodb.com

victoriametrics.com

Technical documentation

docs.aws.amazon.com/redshift

nsdb.io/Architecture

origodb.com/docs

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

Robert Friberg et al

VictoriaMetrics

Initial release

2012

2016

2017

2009

under the name LiveDB

2018

Current release

1703

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

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

Java, Scala

Server operating systems

hosted

Linux

Linux
macOS

Linux
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

optional

yes: int, bigint, decimal, string

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

restricted

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

LDAP

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

Java
Scala

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

depending on model

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

Write ahead log

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

fine grained access rights according to SQL-standard

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.