DBMS > Coveo vs. GeoSpock vs. HEAVY.AI vs. Snowflake vs. TerminusDB

System Properties Comparison Coveo vs. GeoSpock vs. HEAVY.AI vs. Snowflake vs. TerminusDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

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

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

Primary database model

Search engine

Relational DBMS

Graph DBMS

Secondary database models

Time Series DBMS

Spatial DBMS

Document store
RDF store

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.coveo.com

geospock.com

github.com/heavyai/heavydb
www.heavy.ai

www.snowflake.com

terminusdb.com

Technical documentation

docs.coveo.com

docs.heavy.ai

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

Coveo

GeoSpock

HEAVY.AI, Inc.

Snowflake Computing Inc.

DataChemist Ltd.

Initial release

2012

2016

2014

2018

Current release

2.0, September 2019

5.10, January 2022

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

GPL V3

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, Javascript

C++ and CUDA

Prolog, Rust

Server operating systems

hosted

Linux

hosted

Linux

Data scheme

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

yes

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

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.

yes

Secondary indexes

yes

temporal, categorical

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

JDBC

JDBC
ODBC
Thrift
Vega

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C#
Java
JavaScript
Python

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Automatic sharding

Sharding

Round robin

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

granular access controls, API key management, content filters

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

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

Role-based access control

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.