DBMS > Coveo vs. Memcached vs. Quasardb vs. Snowflake vs. SQream DB

System Properties Comparison Coveo vs. Memcached vs. Quasardb vs. Snowflake vs. SQream DB

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

In-memory key-value store, originally intended for caching

Distributed, high-performance timeseries database

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

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

Technical documentation

docs.coveo.com

github.com/memcached/memcached/wiki

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

Coveo

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

quasardb

Snowflake Computing Inc.

SQream Technologies

Initial release

2012

2003

2009

2014

2017

Current release

1.6.27, May 2024

3.14.1, January 2024

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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++

C++, CUDA, Haskell, Java, Scala

Server operating systems

hosted

FreeBSD
Linux
OS X
Unix
Windows

BSD
Linux
OS X
Windows

hosted

Linux

Data scheme

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

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

integer and binary

yes

yes, ANSI Standard SQL Types

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

with tags

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

Proprietary protocol

HTTP API

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

user defined functions in Python

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

consistent hashing

yes

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Repcached, a Memcached patch, provides this functionallity

Source-replica replication with selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

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

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

granular access controls, API key management, content filters

yes

using SASL (Simple Authentication and Security Layer) protocol

Cryptographically strong user authentication and audit trail

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.