DBMS > Coveo vs. GBase vs. Hive vs. IBM Cloudant vs. Snowflake

System Properties Comparison Coveo vs. GBase vs. Hive vs. IBM Cloudant vs. Snowflake

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

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Database as a Service offering based on Apache CouchDB

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.coveo.com

www.gbase.cn

hive.apache.org

www.ibm.com/products/cloudant

www.snowflake.com

Technical documentation

docs.coveo.com

cwiki.apache.org/confluence/display/Hive/Home

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

Developer

Coveo

General Data Technology Co., Ltd.

Apache Software Foundation

initially developed by Facebook

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Snowflake Computing Inc.

Initial release

2012

2004

2012

2010

2014

Current release

GBase 8a, GBase 8s, GBase 8c

3.1.3, April 2022

License

Commercial or Open Source

commercial

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

C, Java, Python

Java

Erlang

Server operating systems

hosted

Linux

All OS with a Java VM

hosted

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

support of semi-structured data formats (JSON, XML, Avro)

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

Secondary indexes

yes

SQL

Support of SQL

Standard with numerous extensions

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
C API
JDBC
ODBC

JDBC
ODBC
Thrift

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

C++
Java
PHP
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions and integration of map-reduce

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

granular access controls, API key management, content filters

yes

Access rights for users, groups and roles

Access rights for users can be defined per database

Users with fine-grained authorization concept, user roles and pluggable authentication

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.