DBMS > Elasticsearch vs. Google BigQuery vs. Teradata Aster vs. Yanza

System Properties Comparison Elasticsearch vs. Google BigQuery vs. Teradata Aster vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Large scale data warehouse service with append-only tables

Platform for big data analytics on multistructured data sources and types

Time Series DBMS for IoT Applications

Primary database model

Search engine

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Website

www.elastic.co/elasticsearch

cloud.google.com/bigquery

yanza.com

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

cloud.google.com/bigquery/docs

Developer

Elastic

Google

Teradata

Yanza

Initial release

2010

2005

2015

Current release

8.6, January 2023

License

Commercial or Open Source

Open Source

Elastic License

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

All OS with a Java VM

hosted

Linux

Windows

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB

HTTP API

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Java
Python
R

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

R packages

Triggers

yes

by using the 'percolation' feature

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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.

Memcached and Redis integration

User concepts

Access control

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.