DBMS > Amazon Neptune vs. Memcached vs. Netezza vs. Snowflake vs. ToroDB

System Properties Comparison Amazon Neptune vs. Memcached vs. Netezza vs. Snowflake vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Fast, reliable graph database built for the cloud

In-memory key-value store, originally intended for caching

Data warehouse and analytics appliance part of IBM PureSystems

Cloud-based data warehousing service for structured and semi-structured data

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

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

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

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	8.59
Rank	#45	Overall
	#29	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

aws.amazon.com/neptune

www.memcached.org

www.ibm.com/products/netezza

www.snowflake.com

github.com/torodb/server

Technical documentation

aws.amazon.com/neptune/developer-resources

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

Developer

Amazon

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

IBM

Snowflake Computing Inc.

8Kdata

Initial release

2017

2003

2000

2014

2016

Current release

1.6.27, May 2024

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

Open Source

AGPL-V3

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

Server operating systems

hosted

FreeBSD
Linux
OS X
Unix
Windows

Linux

included in appliance

hosted

All OS with a Java 7 VM

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

Proprietary protocol

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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.

none

Repcached, a Memcached patch, provides this functionallity

Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

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)

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users and roles

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.