DBMS > Coveo vs. Graphite vs. Microsoft Azure Cosmos DB vs. Snowflake

System Properties Comparison Coveo vs. Graphite vs. Microsoft Azure Cosmos DB vs. Snowflake

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Search engine

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	2.14
Rank	#116	Overall
	#11	Search engines

Score	5.19
Rank	#62	Overall
	#4	Time Series DBMS

Score	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.coveo.com

github.com/graphite-project/graphite-web

azure.microsoft.com/services/cosmos-db

www.snowflake.com

Technical documentation

docs.coveo.com

graphite.readthedocs.io

learn.microsoft.com/azure/cosmos-db

docs.snowflake.net/manuals/index.html

Developer

Coveo

Chris Davis

Microsoft

Snowflake Computing Inc.

Initial release

2012

2006

2014

License

Commercial or Open Source

commercial

Open Source

Apache 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

Python

Server operating systems

hosted

Linux
Unix

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

Numeric data only

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

HTTP API
Sockets

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

CLI Client
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

JavaScript (Node.js)
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

JavaScript

user defined functions

Triggers

yes

JavaScript

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Access rights can be defined down to the item level

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.