DBMS > Drizzle vs. GeoSpock vs. Google BigQuery vs. SiteWhere vs. Solr

System Properties Comparison Drizzle vs. GeoSpock vs. Google BigQuery vs. SiteWhere 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.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

Large scale data warehouse service with append-only tables

M2M integration platform for persisting/querying time series data

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

Primary database model

Relational DBMS

Time Series DBMS

Search engine

Secondary database models

Time Series DBMS

Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

geospock.com

cloud.google.com/bigquery

github.com/sitewhere/sitewhere

solr.apache.org

Technical documentation

cloud.google.com/bigquery/docs

sitewhere1.sitewhere.io/index.html

solr.apache.org/resources.html

Developer

Drizzle project, originally started by Brian Aker

GeoSpock

Google

SiteWhere

Apache Software Foundation

Initial release

2008

2010

2006

Current release

7.2.4, September 2012

2.0, September 2019

9.6.0, April 2024

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

Common Public Attribution License Version 1.0

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, Javascript

Java

Server operating systems

FreeBSD
Linux
OS X

hosted

Linux
OS X
Windows

All OS with a Java VM

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

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

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

temporal, categorical

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

ANSI SQL for query only (using Presto)

yes

Solr Parallel SQL Interface

APIs and other access methods

JDBC

RESTful HTTP/JSON API

HTTP REST

Java API
RESTful HTTP/JSON API

Supported programming languages

C
C++
Java
PHP

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

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

Automatic sharding

none

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

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

Since BigQuery is designed for querying data

optimistic locking

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per table

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Users with fine-grained authorization concept

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.