DBMS > Badger vs. Geode vs. Postgres-XL vs. TimesTen vs. Yanza

System Properties Comparison Badger vs. Geode vs. Postgres-XL vs. TimesTen vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

In-Memory RDBMS compatible to Oracle

Time Series DBMS for IoT Applications

Primary database model

Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

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

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

github.com/dgraph-io/badger

geode.apache.org

www.postgres-xl.org

www.oracle.com/database/technologies/related/timesten.html

yanza.com

Technical documentation

godoc.org/github.com/dgraph-io/badger

geode.apache.org/docs

www.postgres-xl.org/documentation

docs.oracle.com/database/timesten-18.1

Developer

DGraph Labs

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

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Yanza

Initial release

2017

2002

2014

since 2012, originally named StormDB

1998

2015

Current release

1.1, February 2017

10 R1, October 2018

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Mozilla public license

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Windows

Data scheme

schema-free

yes

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.

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

distributed, parallel query execution

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API

Supported programming languages

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C++
Java
PL/SQL

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

PL/SQL

Triggers

yes

Cache Event Listeners

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source 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

none

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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

Access rights per client and object definable

fine grained access rights 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

Recent citations in the news

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

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

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

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

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

provided by Google News

The Intel Xeon E7-8800 v3 Review: The POWER8 Killer?
8 May 2015, AnandTech

provided by Google News

Share this page