DBMS > CouchDB vs. Google BigQuery vs. searchxml vs. Teradata Aster

System Properties Comparison CouchDB vs. Google BigQuery vs. searchxml vs. Teradata Aster

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.

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Large scale data warehouse service with append-only tables

DBMS for structured and unstructured content wrapped with an application server

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

couchdb.apache.org

cloud.google.com/bigquery

www.searchxml.net/category/products

Technical documentation

docs.couchdb.org/en/stable

cloud.google.com/bigquery/docs

www.searchxml.net/support/handouts

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Google

informationpartners gmbh

Teradata

Initial release

2005

2010

2015

2005

Current release

3.3.3, December 2023

1.0

License

Commercial or Open Source

Open Source

Apache version 2

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

Erlang

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Windows

Linux

Data scheme

schema-free

yes

schema-free

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

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

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

via views

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++

most other programming languages supported via APIs

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

in JavaScript

yes

on the application server

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

sychronisation to multiple collections

yes

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a single document possible

Since BigQuery is designed for querying data

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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.

User concepts

Access control

Access rights for users can be defined per database

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

Google Cloud Identity & Access Management (IAM)

Domain, group and role-based access control at the document level and for application services

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.