DBMS > Coveo vs. Google BigQuery vs. Sequoiadb vs. Tkrzw vs. Yaacomo

System Properties Comparison Coveo vs. Google BigQuery vs. Sequoiadb vs. Tkrzw vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

Large scale data warehouse service with append-only tables

NewSQL database with distributed OLTP and SQL

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Search engine

Relational DBMS

Document store
Relational DBMS

Key-value store

Relational DBMS

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.coveo.com

cloud.google.com/bigquery

www.sequoiadb.com

dbmx.net/tkrzw

yaacomo.com

Technical documentation

docs.coveo.com

cloud.google.com/bigquery/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Coveo

Google

Sequoiadb Ltd.

Mikio Hirabayashi

Q2WEB GmbH

Initial release

2012

2010

2013

2020

2009

Current release

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache Version 2.0

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

Server operating systems

hosted

Linux

Linux
macOS

Android
Linux
Windows

Data scheme

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

proprietary protocol using JSON

JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C++
Java
PHP
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

Document is locked during a transaction

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

using specific database classes

yes

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)

simple password-based access control

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.