DBMS > Amazon DocumentDB vs. Drizzle vs. InfinityDB vs. SpaceTime vs. TerarkDB

System Properties Comparison Amazon DocumentDB vs. Drizzle vs. InfinityDB vs. SpaceTime vs. TerarkDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A Java embedded Key-Value Store which extends the Java Map interface

SpaceTime is a spatio-temporal DBMS with a focus on performance.

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

Primary database model

Secondary database models

Relational DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

aws.amazon.com/documentdb

boilerbay.com

www.mireo.com/spacetime

github.com/bytedance/terarkdb

Technical documentation

aws.amazon.com/documentdb/resources

boilerbay.com/infinitydb/manual

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Drizzle project, originally started by Brian Aker

Boiler Bay Inc.

Mireo

ByteDance, originally Terark

Initial release

2019

2008

2002

2020

2016

Current release

7.2.4, September 2012

4.0

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

restricted open source version 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++

Java

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

All OS with a Java VM

Linux

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

schema-free

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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.

Secondary indexes

yes

manual creation possible, using inversions based on multi-value capability

SQL

Support of SQL

yes

with proprietary extensions

A subset of ANSI SQL is implemented

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

RESTful HTTP API

C++ API
Java API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C
C++
Java
PHP

Java

C#
C++
Python

C++
Java

Server-side scripts

Stored procedures

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Fixed-grid hypercubes

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication
Source-replica replication

none

Real-time block device replication (DRBD)

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

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

manual creation possible, using inversions based on multi-value capability

Transaction concepts

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

Atomic single-document operations

ACID

Optimistic locking for transactions; no isolation for bulk loads

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

User concepts

Access control

Access rights for users and roles

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

AWS announces Amazon DocumentDB zero-ETL integration with Amazon OpenSearch Service
16 May 2024, AWS Blog

A hybrid approach for homogeneous migration to an Amazon DocumentDB elastic cluster | Amazon Web Services
4 June 2024, AWS Blog

Use LangChain and vector search on Amazon DocumentDB to build a generative AI chatbot | Amazon Web Services
20 May 2024, AWS Blog

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

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

provided by Google News

A Chinese company is making the cloud 200x faster · TechNode
3 July 2017, TechNode

provided by Google News

Share this page