DBMS > Apache Druid vs. GigaSpaces vs. RocksDB vs. Yanza

System Properties Comparison Apache Druid vs. GigaSpaces vs. RocksDB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS
Time Series DBMS

Document store
Object oriented DBMS

Values are user defined objects

Key-value store

Time Series DBMS

Secondary database models

Graph DBMS
Search engine

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

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

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

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

druid.apache.org

www.gigaspaces.com

rocksdb.org

yanza.com

Technical documentation

druid.apache.org/docs/latest/design

docs.gigaspaces.com/latest/landing.html

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation and contributors

Gigaspaces Technologies

Facebook, Inc.

Yanza

Initial release

2012

2000

2013

2015

Current release

29.0.1, April 2024

15.5, September 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache Version 2; Commercial licenses available

Open Source

BSD

commercial

free version available

Cloud-based only

Only available as a cloud 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

Java

Java, C++, .Net

C++

Server operating systems

Linux
OS X
Unix

Linux
macOS
Solaris
Windows

Linux

Windows

Data scheme

yes

schema-less columns are supported

schema-free

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

SQL-99 for query and DML statements

APIs and other access methods

JDBC
RESTful HTTP/JSON API

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

C++ API
Java API

HTTP API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C++
Java
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Triggers

yes, event driven architecture

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

none

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

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Role-based access control

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.