DBMS > Amazon CloudSearch vs. Google BigQuery vs. TerminusDB vs. Vertica

System Properties Comparison Amazon CloudSearch vs. Google BigQuery vs. TerminusDB vs. Vertica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

Large scale data warehouse service with append-only tables

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Column oriented

Secondary database models

Document store
RDF store

Spatial DBMS
Time Series DBMS

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

Score	1.86
Rank	#133	Overall
	#12	Search engines

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Score	9.62
Rank	#42	Overall
	#26	Relational DBMS

Website

aws.amazon.com/cloudsearch

cloud.google.com/bigquery

terminusdb.com

www.vertica.com

Technical documentation

docs.aws.amazon.com/cloudsearch

cloud.google.com/bigquery/docs

terminusdb.github.io/terminusdb/#

vertica.com/documentation

Developer

Amazon

Google

DataChemist Ltd.

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2012

2010

2018

2005

Current release

11.0.0, January 2023

12.0.3, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Prolog, Rust

C++

Server operating systems

hosted

Linux

Data scheme

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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.

Secondary indexes

yes

all search fields are automatically indexed

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

SQL-like query language (WOQL)

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

HTTP API

RESTful HTTP/JSON API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript
Python

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

none

Graph Partitioning

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Journaling Streams

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

Bi-directional Spark integration

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

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 journaling

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

authentication via encrypted signatures

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

Google Cloud Identity & Access Management (IAM)

Role-based access control

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

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.