DBMS > Drizzle vs. Fujitsu Enterprise Postgres vs. Hawkular Metrics vs. Snowflake

System Properties Comparison Drizzle vs. Fujitsu Enterprise Postgres vs. Hawkular Metrics 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.

Enterprise-grade PostgreSQL-based DBMS with security enhancements such as Transparent Data Encryption and Data Masking, plus high-availability and performance improvement features.

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.37
Rank	#278	Overall
	#128	Relational DBMS

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.postgresql.fastware.com

www.hawkular.org

www.snowflake.com

Technical documentation

www.postgresql.fastware.com/product-manuals

www.hawkular.org/hawkular-metrics/docs/user-guide

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

PostgreSQL Global Development Group, Fujitsu Australia Software Technology

Community supported by Red Hat

Snowflake Computing Inc.

Initial release

2008

2014

Current release

7.2.4, September 2012

Fujitsu Enterprise Postgres 14, January 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

Apache 2.0

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++

Java

Server operating systems

FreeBSD
Linux
OS X

Linux
Windows

Linux
OS X
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

APIs and other access methods

JDBC

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

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

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

Go
Java
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

via Hawkular Alerting

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

partitioning by range, list and by hash

Sharding

based on Cassandra

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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.