DBMS > Drizzle vs. Geode vs. OrigoDB vs. Sadas Engine

System Properties Comparison Drizzle vs. Geode vs. OrigoDB vs. Sadas Engine

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.

Description

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

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

A fully ACID in-memory object graph database

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Relational DBMS

Key-value store

Document store
Object oriented DBMS

Relational DBMS

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

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	0.00
Rank	#385	Overall
	#159	Relational DBMS

Website

geode.apache.org

origodb.com

www.sadasengine.com

Technical documentation

geode.apache.org/docs

origodb.com/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Drizzle project, originally started by Brian Aker

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

Robert Friberg et al

SADAS s.r.l.

Initial release

2008

2002

2009

under the name LiveDB

2006

Current release

7.2.4, September 2012

1.1, February 2017

8.0

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

commercial

free trial version available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Java

C++

Server operating systems

FreeBSD
Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Windows

AIX
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

.NET Client API
HTTP API
LINQ

JDBC
ODBC
Proprietary protocol

Supported programming languages

C
C++
Java
PHP

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

.Net

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

managed by 'Learn by Usage'

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights per client and object definable

Role based authorization

Access rights for users, groups and roles according to SQL-standard

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

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

RDBMS and Apache Geode Data Movement: Low Latency ETL Pipeline by Using Cloud-Native Event Driven Microservices
30 June 2018, InfoQ.com

Chapter 1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode
15 November 2018, O'Reilly Media

HPE buys query acceleration platform Ampool to boost Ezmeral hybrid cloud analytics
7 July 2021, SiliconANGLE News

HPE acquires Ampool to gain distributed SQL engine
9 July 2021, VentureBeat

provided by Google News

Share this page