DBMS > Alibaba Cloud Table Store vs. Amazon DynamoDB vs. Linter vs. Machbase Neo vs. Oracle Berkeley DB

System Properties Comparison Alibaba Cloud Table Store vs. Amazon DynamoDB vs. Linter vs. Machbase Neo vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

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

RDBMS for high security requirements

TimeSeries DBMS for AIoT and BigData

Widely used in-process key-value store

Primary database model

Wide column store

Document store
Key-value store

Relational DBMS

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Spatial DBMS

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

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

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

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/dynamodb

linter.ru

machbase.com

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/dynamodb

machbase.com/dbms

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Alibaba

Amazon

relex.ru

Machbase

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2016

2012

1990

2013

1994

Current release

V8.0, August 2023

18.1.40, May 2020

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

free test version available

Open Source

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

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

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

Linux
macOS
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL interfaced based on SQLite is available

APIs and other access methods

HTTP API

RESTful HTTP API

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

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Supported programming languages

Java
Python

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

by integration with AWS Lambda

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Source-replica replication

selectable replication factor

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

Immediate Consistency

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

Atomic single-row operations

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

volatile and lookup table

yes

User concepts

Access control

Access rights based on subaccounts and tokens

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

fine grained access rights according to SQL-standard

simple password-based access control

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.