DBMS > Amazon Aurora vs. Google BigQuery vs. Ignite vs. Oracle Berkeley DB vs. Teradata

System Properties Comparison Amazon Aurora vs. Google BigQuery vs. Ignite vs. Oracle Berkeley DB vs. Teradata

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Large scale data warehouse service with append-only tables

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Widely used in-process key-value store

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

aws.amazon.com/rds/aurora

cloud.google.com/bigquery

ignite.apache.org

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

www.teradata.com

Technical documentation

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

cloud.google.com/bigquery/docs

apacheignite.readme.io/docs

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

docs.teradata.com

Developer

Amazon

Google

Apache Software Foundation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Teradata

Initial release

2015

2010

2015

1994

1984

Current release

Apache Ignite 2.6

18.1.40, May 2020

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

commercial license 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++, Java, .Net

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

Server operating systems

hosted

Linux
OS X
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted
Linux

Data scheme

yes

schema-free

yes

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

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

yes

SQL interfaced based on SQLite is available

yes

SQL 2016 + extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

.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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes (compute grid and cache interceptors can be used instead)

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

yes (cache interceptors and events)

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

none

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes (replicated cache)

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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)

Security Hooks for custom implementations

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.