DBMS > Amazon Redshift vs. Dolt vs. Drizzle vs. Spark SQL vs. Valentina Server

System Properties Comparison Amazon Redshift vs. Dolt vs. Drizzle vs. Spark SQL vs. Valentina Server

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

A MySQL compatible DBMS with Git-like versioning of data and schema

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Spark SQL is a component on top of 'Spark Core' for structured data processing

Object-relational database and reports server

Primary database model

Relational DBMS

Secondary database models

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

aws.amazon.com/redshift

github.com/dolthub/dolt
www.dolthub.com

spark.apache.org/sql

www.valentina-db.net

Technical documentation

docs.aws.amazon.com/redshift

docs.dolthub.com

spark.apache.org/docs/latest/sql-programming-guide.html

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

Developer

Amazon (based on PostgreSQL)

DoltHub Inc

Drizzle project, originally started by Brian Aker

Apache Software Foundation

Paradigma Software

Initial release

2012

2018

2008

2014

1999

Current release

7.2.4, September 2012

3.5.0 ( 2.13), September 2023

5.7.5

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GNU GPL

Open Source

Apache 2.0

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

C++

Scala

Server operating systems

hosted

Linux
macOS
Windows

FreeBSD
Linux
OS X

Linux
OS X
Windows

Data scheme

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

CLI Client
HTTP REST

JDBC

JDBC
ODBC

ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Java
PHP

Java
Python
R
Scala

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

currently in alpha release

yes

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Concurrency

Support for concurrent manipulation of data

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

fine grained access rights according to SQL-standard

Only one user is configurable, and must be specified in the config file at startup

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.