DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. LokiJS vs. OrientDB

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. LokiJS vs. OrientDB

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

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

In-memory JavaScript DBMS

Multi-model DBMS (Document, Graph, Key/Value)

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Document store
Graph DBMS
Key-value store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.49
Rank	#260	Overall
	#42	Document stores

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Website

aws.amazon.com/redshift

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

github.com/techfort/LokiJS

orientdb.org

Technical documentation

docs.aws.amazon.com/redshift

techfort.github.io/LokiJS

www.orientdb.com/docs/last/index.html

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

OrientDB LTD; CallidusCloud; SAP

Initial release

2012

2016

2014

2010

Current release

1703

3.2.29, March 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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

JavaScript

Java

Server operating systems

hosted

Linux

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

All OS with a Java JDK (>= JDK 6)

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

Typing

predefined data types such as float or date

yes

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

restricted

yes

via views

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language, no joins

APIs and other access methods

JDBC
ODBC

LDAP

JavaScript API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

JavaScript

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

Java, Javascript

Triggers

yes

Hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

relationship in graphs

Transaction concepts

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

ACID

Atomic execution of specific operations

atomic operations within a single collection possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

Access rights for users and roles; record level security configurable

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.