DBMS > Drizzle vs. GigaSpaces vs. SAP HANA vs. ToroDB

System Properties Comparison Drizzle vs. GigaSpaces vs. SAP HANA vs. ToroDB

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.

ToroDB 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.

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

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

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

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Document store

Secondary database models

Graph DBMS
Search engine

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.gigaspaces.com

www.sap.com/products/hana.html

github.com/torodb/server

Technical documentation

docs.gigaspaces.com/latest/landing.html

help.sap.com/hana

Developer

Drizzle project, originally started by Brian Aker

Gigaspaces Technologies

SAP

8Kdata

Initial release

2008

2000

2010

2016

Current release

7.2.4, September 2012

15.5, September 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2; Commercial licenses available

commercial

Open Source

AGPL-V3

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

Java, C++, .Net

Java

Server operating systems

FreeBSD
Linux
OS X

Linux
macOS
Solaris
Windows

Appliance or cloud-service

All OS with a Java 7 VM

Data scheme

yes

schema-free

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-99 for query and DML statements

yes

APIs and other access methods

JDBC

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

.Net
C++
Java
Python
Scala

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

hooks for callbacks inside the server can be used.

yes, event driven architecture

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Eventual Consistency
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

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

Role-based access control

yes

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.