DBMS > Apache Drill vs. Drizzle vs. Kingbase vs. Memcached vs. SAP HANA

System Properties Comparison Apache Drill vs. Drizzle vs. Kingbase vs. Memcached vs. SAP HANA

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

In-memory key-value store, originally intended for caching

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial 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	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.45
Rank	#262	Overall
	#123	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

drill.apache.org

www.kingbase.com.cn

www.memcached.org

www.sap.com/products/hana.html

Technical documentation

drill.apache.org/docs

github.com/memcached/memcached/wiki

help.sap.com/hana

Developer

Apache Software Foundation

Drizzle project, originally started by Brian Aker

BeiJing KINGBASE Information technologies inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SAP

Initial release

2012

2008

1999

2003

2010

Current release

1.20.3, January 2023

7.2.4, September 2012

V8.0, August 2021

1.6.25, March 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GNU GPL

commercial

Open Source

BSD license

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

C++

C and Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux
Windows

FreeBSD
Linux
OS X
Unix
Windows

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

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

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

Standard with numerous extensions

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

Proprietary protocol

JDBC
ODBC

Supported programming languages

C++

C
C++
Java
PHP

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
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

horizontal partitioning (by range, list and hash) and vertical partitioning

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

Repcached, a Memcached patch, provides this functionallity

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

yes

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.