DBMS > Amazon Redshift vs. Axibase vs. Drizzle vs. OrientDB

System Properties Comparison Amazon Redshift vs. Axibase vs. Drizzle vs. OrientDB

Please select another system to include it in the comparison.

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

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
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.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Website

aws.amazon.com/redshift

axibase.com/docs/atsd/finance

orientdb.org

Technical documentation

docs.aws.amazon.com/redshift

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

Developer

Amazon (based on PostgreSQL)

Axibase Corporation

Drizzle project, originally started by Brian Aker

OrientDB LTD; CallidusCloud; SAP

Initial release

2012

2013

2008

2010

Current release

15585

7.2.4, September 2012

3.2.29, March 2024

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

GNU GPL

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

C++

Java

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X

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

Data scheme

yes

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

short, integer, long, float, double, decimal, string

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

SQL-like query language

yes

with proprietary extensions

SQL-like query language, no joins

APIs and other access methods

JDBC
ODBC

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

JDBC

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

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
PHP
Python
R
Ruby

C
C++
Java
PHP

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Java, Javascript

Triggers

yes

hooks for callbacks inside the server can be used.

Hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

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

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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.