DBMS > Apache Phoenix vs. Drizzle vs. GridDB vs. SAP HANA

System Properties Comparison Apache Phoenix vs. Drizzle vs. GridDB vs. SAP HANA

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

Scalable in-memory time series database optimized for IoT and Big Data

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

phoenix.apache.org

griddb.net

www.sap.com/products/hana.html

Technical documentation

phoenix.apache.org

docs.griddb.net

help.sap.com/hana

Developer

Apache Software Foundation

Drizzle project, originally started by Brian Aker

Toshiba Corporation

SAP

Initial release

2014

2008

2013

2010

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

7.2.4, September 2012

5.1, August 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Server operating systems

Linux
Unix
Windows

FreeBSD
Linux
OS X

Linux

Appliance or cloud-service

Data scheme

yes

late-bound, schema-on-read capabilities

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

JDBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

C
C++
Java
PHP

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID at container level

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.

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per database

yes

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.