DBMS > Amazon DynamoDB vs. Drizzle vs. Ehcache vs. Infobright

System Properties Comparison Amazon DynamoDB vs. Drizzle vs. Ehcache vs. Infobright

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

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

A widely adopted Java cache with tiered storage options

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Relational DBMS

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

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Website

aws.amazon.com/dynamodb

www.ehcache.org

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

docs.aws.amazon.com/dynamodb

www.ehcache.org/documentation

Developer

Amazon

Drizzle project, originally started by Brian Aker

Terracotta Inc, owned by Software AG

Ignite Technologies Inc.; formerly InfoBright Inc.

Initial release

2012

2008

2009

2005

Current release

7.2.4, September 2012

3.10.0, March 2022

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 licenses available

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

FreeBSD
Linux
OS X

All OS with a Java VM

Linux
Windows

Data scheme

schema-free

yes

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

Knowledge Grid Technology used instead

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP API

JDBC

JCache

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Java
PHP

Java

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Triggers

yes

by integration with AWS Lambda

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

Source-replica 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

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

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

ACID

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.