DBMS > Coveo vs. EXASOL vs. GridGain vs. RDFox vs. Snowflake

System Properties Comparison Coveo vs. EXASOL vs. GridGain vs. RDFox 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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

GridGain is an in-memory computing platform, built on Apache Ignite

High performance knowledge graph and semantic reasoning engine

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

Primary database model

Search engine

Relational DBMS

Key-value store
Relational DBMS

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Relational DBMS

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.29
Rank	#300	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.coveo.com

www.exasol.com

www.gridgain.com

www.oxfordsemantic.tech

www.snowflake.com

Technical documentation

docs.coveo.com

www.exasol.com/resources

www.gridgain.com/docs/index.html

docs.oxfordsemantic.tech

docs.snowflake.net/manuals/index.html

Developer

Coveo

Exasol

GridGain Systems, Inc.

Oxford Semantic Technologies

Snowflake Computing Inc.

Initial release

2012

2000

2007

2017

2014

Current release

GridGain 8.5.1

6.0, Septermber 2022

License

Commercial or Open Source

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

Java, C++, .Net

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

hosted

Data scheme

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

yes

RDF schemas

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

yes

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

RESTful HTTP API
SPARQL 1.1

CLI Client
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

Java
Lua
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

C
Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

replication via a shared file system

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in stand-alone mode, Eventual Consistency in replicated setups

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 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, groups and roles according to SQL-standard

Security Hooks for custom implementations

Roles, resources, and access types

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.