DBMS > Amazon Redshift vs. Drizzle vs. SiteWhere vs. Solr vs. YTsaurus

System Properties Comparison Amazon Redshift vs. Drizzle vs. SiteWhere vs. Solr vs. YTsaurus

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

Large scale data warehouse service for use with business intelligence tools

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

M2M integration platform for persisting/querying time series data

A widely used distributed, scalable search engine based on Apache Lucene

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Relational DBMS

Time Series DBMS

Search engine

Document store
Key-value store

Secondary database models

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	0.11
Rank	#340	Overall
	#45	Document stores
	#50	Key-value stores

Website

aws.amazon.com/redshift

github.com/sitewhere/sitewhere

solr.apache.org

ytsaurus.tech

Technical documentation

docs.aws.amazon.com/redshift

sitewhere1.sitewhere.io/index.html

solr.apache.org/resources.html

ytsaurus.tech/docs/en

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

SiteWhere

Apache Software Foundation

Yandex

Initial release

2012

2008

2010

2006

2023

Current release

7.2.4, September 2012

9.6.0, April 2024

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Common Public Attribution License Version 1.0

Open Source

Apache Version 2

Open Source

Apache License, Version 2.0

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

hosted

FreeBSD
Linux
OS X

Linux
OS X
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Ubuntu

Data scheme

yes

predefined scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

restricted

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

Solr Parallel SQL Interface

YQL, an SQL-based language, is supported

APIs and other access methods

JDBC
ODBC

JDBC

HTTP REST

Java API
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Java plugins

Triggers

hooks for callbacks inside the server can be used.

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

optimistic locking

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

User concepts

Access control

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users with fine-grained authorization concept

yes

Access Control Lists

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.