DBMS > Amazon DynamoDB vs. JaguarDB vs. Linter vs. Percona Server for MySQL vs. RavenDB

System Properties Comparison Amazon DynamoDB vs. JaguarDB vs. Linter vs. Percona Server for MySQL vs. RavenDB

Editorial information provided by DB-Engines

Name

Description

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

Performant, highly scalable DBMS for AI and IoT applications

RDBMS for high security requirements

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Document store
Key-value store

Key-value store
Vector DBMS

Relational DBMS

Document store

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

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

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	2.10
Rank	#119	Overall
	#57	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

aws.amazon.com/dynamodb

www.jaguardb.com

linter.ru

www.percona.com/software/mysql-database/percona-server

ravendb.net

Technical documentation

docs.aws.amazon.com/dynamodb

www.jaguardb.com/support.html

www.percona.com/downloads/Percona-Server-LATEST

ravendb.net/docs

Developer

Amazon

DataJaguar, Inc.

relex.ru

Percona

Hibernating Rhinos

Initial release

2012

2015

1990

2008

2010

Current release

3.3 July 2023

8.0.36-28, 2024

5.4, July 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

GPL V3.0

commercial

Open Source

GPL version 2

Open Source

AGPL version 3, commercial license available

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

the server part. Clients available in other languages

C and C++

Server operating systems

hosted

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

SQL-like query language (RQL)

APIs and other access methods

RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

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

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

Triggers

yes

by integration with AWS Lambda

yes

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-source replication

Source-replica replication

Multi-source replication
Source-replica replication
XtraDB Cluster

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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)

rights management via user accounts

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Authorization levels configured per client per database

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.