DBMS > Amazon DynamoDB vs. Informix vs. LevelDB vs. TerarkDB vs. Yanza

System Properties Comparison Amazon DynamoDB vs. Informix vs. LevelDB vs. TerarkDB vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

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

A secure embeddable database from IBM, positioned besides IBM Db2 as a relatively low-cost product optimized for OLTP and Internet of Things data

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store

Relational DBMS

Since Version 12.10 support for JSON/BSON datatypes compatible with MongoDB

Key-value store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS

with Informix TimeSeries Extension

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

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

Score	16.32
Rank	#35	Overall
	#21	Relational DBMS

Score	2.33
Rank	#111	Overall
	#19	Key-value stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

aws.amazon.com/dynamodb

www.ibm.com/products/informix

github.com/google/leveldb

github.com/bytedance/terarkdb

yanza.com

Technical documentation

docs.aws.amazon.com/dynamodb

informix.hcldoc.com
www.ibm.com/support/knowledgecenter/SSGU8G/welcomeIfxServers.html

github.com/google/leveldb/blob/main/doc/index.md

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon

IBM, HCL Technologies

Effective May 1st, 2017, HCL took on development, technical support, and product management teams, and works jointly with IBM on product strategy, marketing, and sales.

Google

ByteDance, originally Terark

Yanza

Initial release

2012

1984

2011

2016

2015

Current release

14.10.FC5, November 2020

1.23, February 2021

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

free developer edition available

Open Source

BSD

commercial

restricted open source version available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, C++ and Java

C++

Server operating systems

hosted

AIX
HP-UX
Linux
macOS
Solaris
Windows

Illumos
Linux
OS X
Windows

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Since Version 12.10 support for JSON/BSON datatypes

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

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

JDBC
JSON API

MongoDB compatible
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

C++ API
Java API

HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C++
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

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

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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)

Users with fine-grained authentication, authorization, and auditing controls

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.