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

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

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

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

Analytics Platform for Big Data

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Search engine

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

Score	0.60
Rank	#247	Overall
	#113	Relational DBMS

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

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

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

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

www.snowflake.com

www.splunk.com

Technical documentation

github.com/apache/doris/wiki

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

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation, originally contributed from Baidu

Oracle

Snowflake Computing Inc.

Splunk Inc.

Initial release

2017

2011

2014

2003

Current release

1.2.2, February 2023

24.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

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

commercial

Limited free edition and free developer edition available

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

Linux
Solaris SPARC/x86

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

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

yes

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

yes

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

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
MySQL client

RESTful HTTP API

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

Java

C
C#
Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

configurable

ACID within a storage node (=shard)

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

Access rights for users and roles

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.