DBMS > Amazon DynamoDB vs. Amazon Neptune vs. Drizzle vs. VictoriaMetrics

System Properties Comparison Amazon DynamoDB vs. Amazon Neptune vs. Drizzle vs. VictoriaMetrics

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

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

Fast, reliable graph database built for the cloud

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

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Document store
Key-value store

Graph DBMS
RDF store

Relational DBMS

Time Series DBMS

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

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

Score	2.20
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	1.23
Rank	#165	Overall
	#15	Time Series DBMS

Website

aws.amazon.com/dynamodb

aws.amazon.com/neptune

victoriametrics.com

Technical documentation

docs.aws.amazon.com/dynamodb

aws.amazon.com/neptune/developer-resources

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Amazon

Drizzle project, originally started by Brian Aker

VictoriaMetrics

Initial release

2012

2017

2008

2018

Current release

7.2.4, September 2012

v1.91, May 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

GNU GPL

Open Source

Apache Version 2.0

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++

Server operating systems

hosted

FreeBSD
Linux
OS X

FreeBSD
Linux
macOS
OpenBSD

Data scheme

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

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

C
C++
Java
PHP

Server-side scripts

Stored procedures

Triggers

yes

by integration with AWS Lambda

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

Multi-source replication
Source-replica replication

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

with encyption-at-rest

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

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.