DBMS > Alibaba Cloud MaxCompute vs. BigchainDB vs. GeoMesa vs. Oracle Berkeley DB vs. RocksDB

System Properties Comparison Alibaba Cloud MaxCompute vs. BigchainDB vs. GeoMesa vs. Oracle Berkeley DB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

MaxCompute (previously known as ODPS) is a general purpose, fully managed, multi-tenancy data processing platform for large-scale data warehousing

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Widely used in-process key-value store

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

a graph-processing framework is available with the graphs being stored in tables

Document store

Spatial DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

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

Score	0.84
Rank	#209	Overall
	#98	Relational DBMS

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.alibabacloud.com/product/maxcompute

www.bigchaindb.com

www.geomesa.org

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

rocksdb.org

Technical documentation

www.alibabacloud.com/help/en/maxcompute

bigchaindb.readthedocs.io/en/latest

www.geomesa.org/documentation/stable/user/index.html

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

github.com/facebook/rocksdb/wiki

Developer

Alibaba

CCRi and others

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Initial release

2016

2014

1994

2013

Current release

5.0.0, May 2024

18.1.40, May 2020

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Apache License 2.0

Open Source

commercial license available

Open Source

BSD

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

Python

Scala

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

C++

Server operating systems

hosted

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

yes

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

SQL-like query language

yes

SQL interfaced based on SQLite is available

APIs and other access methods

Fluentd
Flume
MaxCompute Console

CLI Client
RESTful HTTP API

C++ API
Java API

Supported programming languages

Java

Go
Haskell
Java
JavaScript
Python
Ruby

.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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Java

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

depending on storage layer

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

selectable replication factor

depending on storage layer

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

Access rights for users and roles

yes

depending on the DBMS used for storage

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.