DBMS > Amazon Aurora vs. Dragonfly vs. Ehcache vs. Snowflake

System Properties Comparison Amazon Aurora vs. Dragonfly vs. Ehcache vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

A widely adopted Java cache with tiered storage options

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

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

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

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

aws.amazon.com/rds/aurora

github.com/dragonflydb/dragonfly
www.dragonflydb.io

www.ehcache.org

www.snowflake.com

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

www.dragonflydb.io/docs

www.ehcache.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Amazon

DragonflyDB team and community contributors

Terracotta Inc, owned by Software AG

Snowflake Computing Inc.

Initial release

2015

2023

2009

2014

Current release

1.0, March 2023

3.10.0, March 2022

License

Commercial or Open Source

commercial

Open Source

BSL 1.1

Open Source

Apache Version 2; commercial licenses available

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

Java

Server operating systems

hosted

Linux

All OS with a Java VM

hosted

Data scheme

yes

scheme-free

schema-free

yes

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

Typing

predefined data types such as float or date

yes

strings, hashes, lists, sets, sorted sets, bit arrays

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protocol

JCache

CLI Client
JDBC
ODBC

Supported programming languages

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

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Lua

user defined functions

Triggers

yes

publish/subscribe channels provide some trigger functionality

yes

Cache Event Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

by using Terracotta Server

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

by using Terracotta Server

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Password-based authentication

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

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.