DBMS > Coveo vs. Elasticsearch vs. Google BigQuery vs. NuoDB

System Properties Comparison Coveo vs. Elasticsearch vs. Google BigQuery vs. NuoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Primary database model

Search engine

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.89
Rank	#198	Overall
	#92	Relational DBMS

Website

www.coveo.com

www.elastic.co/elasticsearch

cloud.google.com/bigquery

www.3ds.com/nuodb-distributed-sql-database

Technical documentation

docs.coveo.com

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

cloud.google.com/bigquery/docs

doc.nuodb.com

Developer

Coveo

Elastic

Google

Dassault Systèmes

originally NuoDB, Inc.

Initial release

2012

2010

2013

Current release

8.6, January 2023

License

Commercial or Open Source

commercial

Open Source

Elastic License

commercial

limited edition free

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

Server operating systems

hosted

All OS with a Java VM

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

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

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.

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

Java API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Java, SQL

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

data is dynamically stored/cached on the nodes where it is read/written

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Managed transparently by NuoDB

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Since BigQuery is designed for querying data

ACID

tunable commit protocol

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

yes

Temporary table

User concepts

Access control

granular access controls, API key management, content filters

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

Google Cloud Identity & Access Management (IAM)

Standard SQL roles/ privileges, Administrative Users

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.