DBMS > Amazon DocumentDB vs. Atos Standard Common Repository vs. BigObject vs. Tarantool

System Properties Comparison Amazon DocumentDB vs. Atos Standard Common Repository vs. BigObject vs. Tarantool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Analytic DBMS for real-time computations and queries

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

Primary database model

Document store

Document store
Key-value store

Relational DBMS

a hierachical model (tree) can be imposed

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.91
Rank	#132	Overall
	#24	Document stores

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

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

Website

aws.amazon.com/documentdb

atos.net/en/convergence-creators/portfolio/standard-common-repository

bigobject.io

www.tarantool.io

Technical documentation

aws.amazon.com/documentdb/resources

docs.bigobject.io

www.tarantool.io/en/doc

Developer

Atos Convergence Creators

BigObject, Inc.

Initial release

2019

2016

2015

2008

Current release

1703

2.10.0, May 2022

License

Commercial or Open Source

commercial

free community edition available

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

Java

C and C++

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

BSD
Linux
macOS

Data scheme

schema-free

Schema and schema-less with LDAP views

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

optional

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

Full-featured ANSI SQL support

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

LDAP

fluentd
ODBC
RESTful HTTP API

Open binary protocol

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

All languages with LDAP bindings

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

Server-side scripts

Stored procedures

Lua

Lua, C and SQL stored procedures

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

none

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

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

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

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

none

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

typically not used, however similar functionality with DBRef possible

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

Atomic single-document operations

Atomic execution of specific operations

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

Read/write lock on objects (tables, trees)

yes, cooperative multitasking

Durability

Support for making data persistent

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

LDAP bind authentication

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Data processing speed and reliability: in-memory synchronous replication
9 November 2021, Vladimir Perepelytsya, Tarantool (sponsor)

show all

Recent citations in the news

Vector search for Amazon DocumentDB (with MongoDB compatibility) is now generally available | Amazon Web Services
29 November 2023, AWS Blog

AWS announces Amazon DocumentDB I/O-Optimized
21 November 2023, AWS Blog

AWS announces vector search for Amazon DocumentDB
29 November 2023, AWS Blog

Reduce cost and improve performance by migrating to Amazon DocumentDB 5.0 | Amazon Web Services
15 April 2024, AWS Blog

Mask sensitive Amazon DocumentDB log data with Amazon CloudWatch Logs data protection | Amazon Web Services
16 April 2024, AWS Blog

provided by Google News

In-Memory Showdown: Redis vs. Tarantool
4 April 2023, Хабр

TaranHouse: New Big Data Warehouse Announced by Tarantool
4 April 2018, Newswire

Deploying Tarantool Cartridge applications with zero effort (Part 1)
16 December 2019, Хабр

Deploying Tarantool Cartridge applications with zero effort (Part 2)
13 April 2020, Хабр

Тarantool Cartridge: Sharding Lua Backend in Three Lines
9 October 2019, Хабр

provided by Google News

Share this page