DBMS > Drizzle vs. RDF4J vs. SiteWhere vs. Snowflake vs. Solr

System Properties Comparison Drizzle vs. RDF4J vs. SiteWhere vs. Snowflake vs. Solr

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.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

M2M integration platform for persisting/querying time series data

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

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

Primary database model

Secondary database models

Spatial DBMS

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

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

rdf4j.org

github.com/sitewhere/sitewhere

www.snowflake.com

solr.apache.org

Technical documentation

rdf4j.org/documentation

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

Developer

Drizzle project, originally started by Brian Aker

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

SiteWhere

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2008

2004

2010

2014

2006

Current release

7.2.4, September 2012

9.6.0, April 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Common Public Attribution License Version 1.0

commercial

Open Source

Apache Version 2

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

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Unix
Windows

Linux
OS X
Windows

hosted

All OS with a Java VM

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

Data scheme

yes

RDF Schemas

predefined scheme

yes

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

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

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

All search fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

yes

Solr Parallel SQL Interface

APIs and other access methods

JDBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

HTTP REST

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

C
C++
Java
PHP

Java
PHP
Python

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

user defined functions

Java plugins

Triggers

hooks for callbacks inside the server can be used.

yes

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable authentication

yes

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.