DBMS > Google BigQuery vs. GreptimeDB vs. MySQL vs. Oracle vs. Tarantool

System Properties Comparison Google BigQuery vs. GreptimeDB vs. MySQL vs. Oracle vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

An open source Time Series DBMS built for increased scalability, high performance and efficiency

Widely used open source RDBMS

Widely used RDBMS

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Spatial DBMS

with Tarantool/GIS extension

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.06
Rank	#352	Overall
	#33	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

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

Website

cloud.google.com/bigquery

greptime.com

www.mysql.com

www.oracle.com/database

www.tarantool.io

Technical documentation

cloud.google.com/bigquery/docs

docs.greptime.com

dev.mysql.com/doc

docs.oracle.com/en/database

www.tarantool.io/en/doc

Developer

Google

Greptime Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

Initial release

2010

2022

1995

1980

2008

Current release

8.4.0, April 2024

23c, September 2023

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted free version is 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Rust

C and C++

Server operating systems

hosted

Android
Docker
FreeBSD
Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

BSD
Linux
macOS

Data scheme

yes

schema-free, schema definition possible

yes

Schemaless in JSON and XML columns

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

Full-featured ANSI SQL support

APIs and other access methods

RESTful HTTP/JSON API

gRPC
HTTP API
JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Open binary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Erlang
Go
Java
JavaScript

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Python

yes

proprietary syntax

PL/SQL

also stored procedures in Java possible

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, horizontal partitioning

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-source replication
Source-replica replication

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

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

not for MyISAM storage engine

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

not for MyISAM storage engine

ACID

isolation level can be parameterized

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

table locks or row locks depending on storage engine

yes

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Simple rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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

Specific characteristics

GreptimeDB is a SQL & Python-enabled timeseries database system built from scratch...
» more

Competitive advantages

- Inherits advantages of Rust, such as excellent performance, memory safe, resource...
» more

Typical application scenarios

For IoT industries, GreptimeDB can seamless integrate with message queues and other...
» more

Key customers

Greptime's clients span multiple sectors including IoT, connected vehicles, and energy...
» more

Market metrics

GreptimeDB has garnered global recognition by topping GitHub trends following its...
» more

Licensing and pricing models

GreptimeDB: open source, distributed, cloud-native TSDB; supports Hybrid Time-series...
» more

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.