DBMS > Drizzle vs. GBase vs. GeoSpock vs. KeyDB

System Properties Comparison Drizzle vs. GBase vs. GeoSpock vs. KeyDB

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.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Spatial and temporal data processing engine for extreme data scale

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Primary database model

Relational DBMS

Key-value store

Secondary database models

Time Series DBMS

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

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Website

www.gbase.cn

geospock.com

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

docs.keydb.dev

Developer

Drizzle project, originally started by Brian Aker

General Data Technology Co., Ltd.

GeoSpock

EQ Alpha Technology Ltd.

Initial release

2008

2004

2019

Current release

7.2.4, September 2012

GBase 8a, GBase 8s, GBase 8c

2.0, September 2019

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

BSD-3

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C, Java, Python

Java, Javascript

C++

Server operating systems

FreeBSD
Linux
OS X

Linux

hosted

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

temporal, categorical

yes

by using the Redis Search module

SQL

Support of SQL

yes

with proprietary extensions

Standard with numerous extensions

ANSI SQL for query only (using Presto)

APIs and other access methods

JDBC

ADO.NET
C API
JDBC
ODBC

JDBC

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

C
C++
Java
PHP

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

user defined functions

Lua

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

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Access rights for users can be defined per table

simple password-based access control and ACL

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

How GeoSpock is supercharging geospatial analytics
23 February 2021, ComputerWeekly.com

nChain Leads Investment Round in Extreme-scale Data Firm GeoSpock
2 October 2020, AlexaBlockchain

Imagining an 'Everything Connected' World With Geospock | AWS Startups Blog
20 June 2019, AWS Blog

GeoSpock launches Spatial Big Data Platform 2.0
4 September 2019, VanillaPlus

GeoSpock launches pioneering new spatial Big Data platform
27 February 2019, Geospatial World

provided by Google News

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

Share this page