DBMS > Apache Druid vs. BaseX vs. GeoSpock vs. searchxml vs. Snowflake

System Properties Comparison Apache Druid vs. BaseX vs. GeoSpock vs. searchxml vs. Snowflake

Editorial information provided by DB-Engines

Name

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

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Spatial and temporal data processing engine for extreme data scale

DBMS for structured and unstructured content wrapped with an application server

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

Primary database model

Relational DBMS
Time Series DBMS

Native XML DBMS

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

druid.apache.org

basex.org

geospock.com

www.searchxml.net/category/products

www.snowflake.com

Technical documentation

druid.apache.org/docs/latest/design

docs.basex.org

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation and contributors

BaseX GmbH

GeoSpock

informationpartners gmbh

Snowflake Computing Inc.

Initial release

2012

2007

2015

2014

Current release

29.0.1, April 2024

10.7, August 2023

2.0, September 2019

1.0

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

BSD license

commercial

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

Java, Javascript

C++

Server operating systems

Linux
OS X
Unix

Linux
OS X
Windows

hosted

Windows

hosted

Data scheme

yes

schema-less columns are supported

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

XQuery supports types

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

temporal, categorical

yes

SQL

Support of SQL

SQL for querying

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

JDBC

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

on the application server

user defined functions

Triggers

yes

via events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Automatic sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

yes

sychronisation to multiple collections

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

multiple readers, single writer

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.

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Users with fine-grained authorization concept on 4 levels

Access rights for users can be defined per table

Domain, group and role-based access control at the document level and for application services

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

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.