DBMS > Amazon DynamoDB vs. Ehcache vs. Microsoft Azure Table Storage vs. Sadas Engine vs. Solr

System Properties Comparison Amazon DynamoDB vs. Ehcache vs. Microsoft Azure Table Storage vs. Sadas Engine vs. Solr

Editorial information provided by DB-Engines

Name

Description

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

A widely adopted Java cache with tiered storage options

A Wide Column Store for rapid development using massive semi-structured datasets

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Document store
Key-value store

Secondary database models

Spatial 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	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

aws.amazon.com/dynamodb

www.ehcache.org

azure.microsoft.com/en-us/services/storage/tables

www.sadasengine.com

solr.apache.org

Technical documentation

docs.aws.amazon.com/dynamodb

www.ehcache.org/documentation

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

solr.apache.org/resources.html

Developer

Amazon

Terracotta Inc, owned by Software AG

Microsoft

SADAS s.r.l.

Apache Software Foundation

Initial release

2012

2009

2012

2006

Current release

3.10.0, March 2022

8.0

9.6.0, April 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2; commercial licenses available

commercial

free trial version available

Open Source

Apache Version 2

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

C++

Java

Server operating systems

hosted

All OS with a Java VM

hosted

AIX
Linux
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

RESTful HTTP API

JCache

RESTful HTTP API

JDBC
ODBC
Proprietary protocol

Java API
RESTful HTTP/JSON API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

Java plugins

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

Implicit feature of the cloud service

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

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

Eventual 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

yes

supports JTA and can work as an XA resource

optimistic locking

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

managed by 'Learn by Usage'

yes

User concepts

Access control

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

Access rights based on private key authentication or shared access signatures

Access rights for users, groups and roles according to SQL-standard

yes

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.