DBMS > Apache Doris vs. Coveo vs. Oracle NoSQL vs. Snowflake

System Properties Comparison Apache Doris vs. Coveo vs. Oracle NoSQL vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An MPP-based analytics DBMS embracing the MySQL protocol

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

Primary database model

Relational DBMS

Search engine

Document store
Key-value store
Relational DBMS

Relational DBMS

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

Score	0.60
Rank	#247	Overall
	#113	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

doris.apache.org
github.com/apache/doris

www.coveo.com

www.oracle.com/database/nosql/technologies/nosql

www.snowflake.com

Technical documentation

github.com/apache/doris/wiki

docs.coveo.com

docs.oracle.com/en/database/other-databases/nosql-database/index.html

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation, originally contributed from Baidu

Coveo

Oracle

Snowflake Computing Inc.

Initial release

2017

2012

2011

2014

Current release

1.2.2, February 2023

24.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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
Solaris SPARC/x86

hosted

Data scheme

yes

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

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

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

Typing

predefined data types such as float or date

yes

optional

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

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
MySQL client

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Java

C#
Java
JavaScript
Python

C
C#
Go
Java
JavaScript (Node.js)
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

horizontal partitioning

yes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

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

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

fine grained access rights according to SQL-standard

granular access controls, API key management, content filters

Access rights for users and roles

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.