DBMS > Amazon SimpleDB vs. BigchainDB vs. RocksDB vs. Spark SQL vs. Tarantool

System Properties Comparison Amazon SimpleDB vs. BigchainDB vs. RocksDB vs. Spark SQL vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Hosted simple database service by Amazon, with the data stored in the Amazon Cloud.

There is an unrelated product called SimpleDB developed by Edward Sciore

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

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.85
Rank	#138	Overall
	#24	Key-value stores

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

aws.amazon.com/simpledb

Technical documentation

docs.aws.amazon.com/simpledb

bigchaindb.readthedocs.io/en/latest

github.com/facebook/rocksdb/wiki

spark.apache.org/docs/latest/sql-programming-guide.html

www.tarantool.io/en/doc

Developer

Amazon

Facebook, Inc.

Apache Software Foundation

Initial release

2007

2016

2013

2014

2008

Current release

8.11.4, April 2024

3.5.0 ( 2.13), September 2023

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

BSD

Open Source

Apache 2.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C++

Scala

C and C++

Server operating systems

hosted

Linux

Linux
OS X
Windows

BSD
Linux
macOS

Data scheme

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

All columns are indexed automatically

yes

SQL

Support of SQL

SQL-like DML and DDL statements

Full-featured ANSI SQL support

APIs and other access methods

RESTful HTTP API

CLI Client
RESTful HTTP API

C++ API
Java API

JDBC
ODBC

Open binary protocol

Supported programming languages

.Net
C
C++
Erlang
Java
PHP
Python
Ruby
Scala

Go
Haskell
Java
JavaScript
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Java
Python
R
Scala

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

Lua, C and SQL stored procedures

Triggers

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding must be implemented in the application

Sharding

horizontal partitioning

yes, utilizing Spark Core

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

Concurrent data updates can be detected by the application

yes

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

yes

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.