DBMS > Drizzle vs. Newts vs. Quasardb vs. Snowflake vs. Splunk

System Properties Comparison Drizzle vs. Newts vs. Quasardb vs. Snowflake vs. Splunk

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Time Series DBMS based on Cassandra

Distributed, high-performance timeseries database

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

Analytics Platform for Big Data

Primary database model

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

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

opennms.github.io/newts

quasar.ai

www.snowflake.com

www.splunk.com

Technical documentation

github.com/OpenNMS/newts/wiki

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Drizzle project, originally started by Brian Aker

OpenNMS Group

quasardb

Snowflake Computing Inc.

Splunk Inc.

Initial release

2008

2014

2009

2014

2003

Current release

7.2.4, September 2012

3.14.1, January 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache 2.0

commercial

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

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

C++

Java

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Windows

BSD
Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

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

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

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC

HTTP REST
Java API

HTTP API

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

C
C++
Java
PHP

Java

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

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

hooks for callbacks inside the server can be used.

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

consistent hashing

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

Source-replica replication with selectable replication factor

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Cryptographically strong user authentication and audit trail

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.