DBMS > Apache Doris vs. Google BigQuery vs. Linter vs. RRDtool vs. Vitess

System Properties Comparison Apache Doris vs. Google BigQuery vs. Linter vs. RRDtool vs. Vitess

Editorial information provided by DB-Engines

Name

Description

An MPP-based analytics DBMS embracing the MySQL protocol

Large scale data warehouse service with append-only tables

RDBMS for high security requirements

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	0.57
Rank	#244	Overall
	#113	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

doris.apache.org
github.com/apache/doris

cloud.google.com/bigquery

linter.ru

oss.oetiker.ch/rrdtool

vitess.io

Technical documentation

github.com/apache/doris/wiki

cloud.google.com/bigquery/docs

oss.oetiker.ch/rrdtool/doc

vitess.io/docs

Developer

Apache Software Foundation, originally contributed from Baidu

Google

relex.ru

Tobias Oetiker

The Linux Foundation, PlanetScale

Initial release

2017

2010

1990

1999

2013

Current release

1.2.2, February 2023

1.8.0, 2022

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL V2 and FLOSS

Open Source

Apache Version 2.0, commercial licenses 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

Java

C and C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

Linux

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

HP-UX
Linux

Docker
Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JDBC
MySQL client

RESTful HTTP/JSON API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

in-process shared library
Pipes

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.