DBMS > Amazon DocumentDB vs. Google Cloud Datastore vs. MySQL vs. TempoIQ vs. Tibero

System Properties Comparison Amazon DocumentDB vs. Google Cloud Datastore vs. MySQL vs. TempoIQ vs. Tibero

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Widely used open source RDBMS

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.91
Rank	#124	Overall
	#22	Document stores

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.46
Rank	#151	Overall
	#70	Relational DBMS

Website

aws.amazon.com/documentdb

cloud.google.com/datastore

www.mysql.com

tempoiq.com (offline)

us.tmaxsoft.com/products/tibero

Technical documentation

aws.amazon.com/documentdb/resources

cloud.google.com/datastore/docs

dev.mysql.com/doc

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Google

Oracle

since 2010, originally MySQL AB, then Sun

TempoIQ

TmaxSoft

Initial release

2019

2008

1995

2012

2003

Current release

9.0.0, July 2024

7, September 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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 and Assembler

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

with proprietary extensions

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
Java
JavaScript

Node.js
Python
Ruby

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

using Google App Engine

yes

proprietary syntax

Persistent Stored Procedure (PSM)

Triggers

Callbacks using the Google Apps Engine

yes

Realtime Alerts

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

by range, hash, list or composite

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 using Paxos

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Atomic single-document operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

planned for next version

User concepts

Access control

Access rights for users and roles

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users with fine-grained authorization concept

no user groups or roles

simple authentication-based access control

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.