DBMS > Amazon Redshift vs. Graph Engine vs. ScyllaDB vs. Valentina Server

System Properties Comparison Amazon Redshift vs. Graph Engine vs. ScyllaDB vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Cassandra and DynamoDB compatible wide column store

Object-relational database and reports server

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Wide column store

Relational DBMS

Secondary database models

Key-value store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	4.75
Rank	#68	Overall
	#5	Wide column stores

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

aws.amazon.com/redshift

www.graphengine.io

www.scylladb.com

www.valentina-db.net

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

docs.scylladb.com

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

Developer

Amazon (based on PostgreSQL)

Microsoft

ScyllaDB

Paradigma Software

Initial release

2012

2010

2015

1999

Current release

ScyllaDB Open Source 5.4.1, January 2024

5.7.5

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Open Source (AGPL), commercial license available

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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

.NET and C

C++

Server operating systems

hosted

.NET

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

restricted

yes

cluster global secondary indices

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements (CQL)

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

yes, Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Representation of geographical distribution of servers is possible

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Atomicity and isolation are supported for single operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

in-memory tables

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per object

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.