DBMS > Drizzle vs. SAP HANA vs. Sqrrl vs. ToroDB vs. Yanza

System Properties Comparison Drizzle vs. SAP HANA vs. Sqrrl vs. ToroDB vs. Yanza

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.

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Adaptable, secure NoSQL built on Apache Accumulo

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

www.sap.com/products/hana.html

sqrrl.com

github.com/torodb/server

yanza.com

Technical documentation

help.sap.com/hana

Developer

Drizzle project, originally started by Brian Aker

SAP

Amazon

originally Sqrrl Data, Inc.

8Kdata

Yanza

Initial release

2008

2010

2012

2016

2015

Current release

7.2.4, September 2012

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

AGPL-V3

commercial

free version available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

but mainly used as a service provided by Yanza

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

Appliance or cloud-service

Linux

All OS with a Java 7 VM

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes

APIs and other access methods

JDBC

JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

HTTP API

Supported programming languages

C
C++
Java
PHP

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

any language that supports HTTP calls

Server-side scripts

Stored procedures

SQLScript, R

Triggers

hooks for callbacks inside the server can be used.

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

making use of Hadoop

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

selectable replication factor

making use of Hadoop

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

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

yes

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

Access rights for users and roles

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.