DBMS > Amazon Aurora vs. Apache Doris vs. Google BigQuery vs. Linter vs. Oracle Berkeley DB

System Properties Comparison Amazon Aurora vs. Apache Doris vs. Google BigQuery vs. Linter vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

An MPP-based analytics DBMS embracing the MySQL protocol

Large scale data warehouse service with append-only tables

RDBMS for high security requirements

Widely used in-process key-value store

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Document store

Spatial DBMS

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

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	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

aws.amazon.com/rds/aurora

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

cloud.google.com/bigquery

linter.ru

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

github.com/apache/doris/wiki

cloud.google.com/bigquery/docs

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Amazon

Apache Software Foundation, originally contributed from Baidu

Google

relex.ru

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2015

2017

2010

1990

1994

Current release

1.2.2, February 2023

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

commercial license 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++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

Linux

hosted

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

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
MySQL client

RESTful HTTP/JSON API

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

Supported programming languages

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

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

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

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

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.