DBMS > Drizzle vs. IBM Db2 Event Store vs. searchxml vs. Snowflake

System Properties Comparison Drizzle vs. IBM Db2 Event Store vs. searchxml vs. Snowflake

Please select another system to include it in the comparison.

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.

Distributed Event Store optimized for Internet of Things use cases

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

Event Store
Time Series DBMS

Native XML DBMS
Search engine

Relational DBMS

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

Score	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.ibm.com/products/db2-event-store

www.searchxml.net/category/products

www.snowflake.com

Technical documentation

www.ibm.com/docs/en/db2-event-store

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

IBM

informationpartners gmbh

Snowflake Computing Inc.

Initial release

2008

2017

2015

2014

Current release

7.2.4, September 2012

2.0

1.0

License

Commercial or Open Source

Open Source

GNU GPL

commercial

free developer edition available

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

C++

C and C++

C++

Server operating systems

FreeBSD
Linux
OS X

Linux

Linux, macOS, Windows for the developer addition

Windows

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

with proprietary extensions

yes

through the embedded Spark runtime

yes

APIs and other access methods

JDBC

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
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

hooks for callbacks inside the server can be used.

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Active-active shard replication

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

fine grained access rights according to SQL-standard

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.