DBMS > Amazon DynamoDB vs. Drizzle vs. Riak KV vs. Sphinx vs. Vertica

System Properties Comparison Amazon DynamoDB vs. Drizzle vs. Riak KV vs. Sphinx vs. Vertica

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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

Distributed, fault tolerant key-value store

Open source search engine for searching in data from different sources, e.g. relational databases

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Search engine

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	10.06
Rank	#42	Overall
	#26	Relational DBMS

Website

aws.amazon.com/dynamodb

sphinxsearch.com

www.vertica.com

Technical documentation

docs.aws.amazon.com/dynamodb

www.tiot.jp/riak-docs/riak/kv/latest

sphinxsearch.com/docs

vertica.com/documentation

Developer

Amazon

Drizzle project, originally started by Brian Aker

OpenSource, formerly Basho Technologies

Sphinx Technologies Inc.

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2012

2008

2009

2001

2005

Current release

7.2.4, September 2012

3.2.0, December 2022

3.5.1, February 2023

12.0.3, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

GNU GPL

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPL version 2, commercial licence available

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Erlang

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux
OS X

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

schema-free

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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

yes

restricted

yes

full-text index on all search fields

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (SphinxQL)

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

RESTful HTTP API

JDBC

HTTP API
Native Erlang Interface

Proprietary protocol

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Java
PHP

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

Erlang

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

by integration with AWS Lambda

hooks for callbacks inside the server can be used.

yes

pre-commit hooks and post-commit hooks

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Sharding

Partitioning is done manually, search queries against distributed index is supported

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

none

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

In-memory capabilities

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

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes, using Riak Security

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

Specific characteristics

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Licensing and pricing models

Cost-based models and subscription-based models are both available. One license is...
» 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.