DBMS > Coveo vs. Lovefield vs. Snowflake vs. Stardog

System Properties Comparison Coveo vs. Lovefield vs. Snowflake vs. Stardog

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

Embeddable relational database for web apps written in pure JavaScript

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Search engine

Relational DBMS

Graph DBMS
RDF store

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

www.coveo.com

google.github.io/lovefield

www.snowflake.com

www.stardog.com

Technical documentation

docs.coveo.com

github.com/google/lovefield/blob/master/docs/spec_index.md

docs.snowflake.net/manuals/index.html

docs.stardog.com

Developer

Coveo

Google

Snowflake Computing Inc.

Stardog-Union

Initial release

2012

2014

2010

Current release

2.1.12, February 2017

7.3.0, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

JavaScript

Java

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

hosted

Linux
macOS
Windows

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)

schema-free and OWL/RDFS-schema support

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

RESTful HTTP API

CLI Client
JDBC
ODBC

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

C#
Java
JavaScript
Python

JavaScript

JavaScript (Node.js)
Python

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

Using read-only observers

similar concept for controling cloud resources

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

yes

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

granular access controls, API key management, content filters

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

Access rights for users and roles

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.