DBMS > Drizzle vs. Galaxybase vs. Geode vs. TerarkDB vs. Yanza

System Properties Comparison Drizzle vs. Galaxybase vs. Geode vs. TerarkDB 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.

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.

Scalable, ACID-compliant native distributed parallel graph platform

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Time Series DBMS for IoT Applications

Primary database model

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

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

galaxybase.com

geode.apache.org

github.com/bytedance/terarkdb

yanza.com

Technical documentation

geode.apache.org/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Drizzle project, originally started by Brian Aker

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

ByteDance, originally Terark

Yanza

Initial release

2008

2017

2002

2016

2015

Current release

7.2.4, September 2012

Nov 20, November 2021

1.1, February 2017

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

restricted open source version available

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

C++

C and Java

Java

C++

Server operating systems

FreeBSD
Linux
OS X

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Windows

Data scheme

yes

Strong typed schema

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (OQL)

APIs and other access methods

JDBC

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

HTTP API

Supported programming languages

C
C++
Java
PHP

Go
Java
Python

.Net
All JVM based languages
C++
Groovy
Java
Scala

C++
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined procedures and functions

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

yes, on a single node

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

Access rights per client and object definable

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

做国产图数据库，「创邻科技」将拓展国际市场| 新科技创业
5 April 2023, 36kr

创邻科技，位居IDC MarketScape中国图数据库市场领导者类别
13 September 2023, CSDN

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Share this page