DBMS > Apache Kylin vs. Coveo vs. SiteWhere vs. Snowflake

System Properties Comparison Apache Kylin vs. Coveo vs. SiteWhere vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

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

M2M integration platform for persisting/querying time series data

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

Primary database model

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

Score	1.25
Rank	#170	Overall
	#77	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

kylin.apache.org

www.coveo.com

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

kylin.apache.org/docs

docs.coveo.com

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation, originally contributed from eBay Inc

Coveo

SiteWhere

Snowflake Computing Inc.

Initial release

2015

2012

2010

2014

Current release

3.1.0, July 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Common Public Attribution License Version 1.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

Java

Server operating systems

Linux

hosted

Linux
OS X
Windows

hosted

Data scheme

yes

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

predefined scheme

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

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Users with fine-grained authorization concept

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.