DBMS > Drizzle vs. Ignite vs. Postgres-XL vs. SiteWhere

System Properties Comparison Drizzle vs. Ignite vs. Postgres-XL vs. SiteWhere

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.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

ignite.apache.org

www.postgres-xl.org

github.com/sitewhere/sitewhere

Technical documentation

apacheignite.readme.io/docs

www.postgres-xl.org/documentation

sitewhere1.sitewhere.io/index.html

Developer

Drizzle project, originally started by Brian Aker

Apache Software Foundation

SiteWhere

Initial release

2008

2015

2014

since 2012, originally named StormDB

2010

Current release

7.2.4, September 2012

Apache Ignite 2.6

10 R1, October 2018

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

Mozilla public license

Open Source

Common Public Attribution License Version 1.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C++, Java, .Net

Java

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Solaris
Windows

Linux
macOS

Linux
OS X
Windows

Data scheme

yes

predefined scheme

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

ANSI-99 for query and DML statements, subset of DDL

yes

distributed, parallel query execution

APIs and other access methods

JDBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP REST

Supported programming languages

C
C++
Java
PHP

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes (replicated cache)

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

ACID

MVCC

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Showcases Power of Apache Ignite at Community Over Code Conference
5 October 2023, Datanami

Apache Ignite: Distributed Database
18 August 2015, ignite.apache.org

Apache Ignite: An Overview
6 September 2023, Open Source For You

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page