DBMS > Geode vs. NSDb vs. Oracle Berkeley DB vs. Yanza

System Properties Comparison Geode vs. NSDb vs. Oracle Berkeley DB 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

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Widely used in-process key-value store

Time Series DBMS for IoT Applications

Primary database model

Key-value store

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

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

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

geode.apache.org

nsdb.io

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

yanza.com

Technical documentation

geode.apache.org/docs

nsdb.io/Architecture

docs.oracle.com/cd/E17076_05/html/index.html

Developer

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

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Yanza

Initial release

2002

2017

1994

2015

Current release

1.1, February 2017

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2.0

Open Source

commercial license 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

Java

Java, Scala

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

only with the Berkeley DB XML edition

Secondary indexes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

yes

SQL interfaced based on SQLite is available

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

gRPC
HTTP REST
WebSocket

HTTP API

Supported programming languages

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

Java
Scala

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

yes

only for the SQL API

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

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

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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

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

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

Victor I. Cazares Wants NYTW to Call for Ceasefire in Gaza
22 February 2024, Vulture

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, O'Reilly Media

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

provided by Google News

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

Margo I. Seltzer | Berkman Klein Center
18 August 2020, Berkman Klein Center

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

How to store financial market data for backtesting
26 January 2019, Towards Data Science

The importance of bitcoin nodes and how to start one
9 May 2014, The Merkle News

provided by Google News

Share this page