DBMS > BigObject vs. Derby vs. Geode vs. Postgres-XL

System Properties Comparison BigObject vs. Derby vs. Geode vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

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

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

Technical documentation

docs.bigobject.io

db.apache.org/derby/manuals/index.html

geode.apache.org/docs

www.postgres-xl.org/documentation

Developer

BigObject, Inc.

Apache Software Foundation

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

Initial release

2015

1997

2002

2014

since 2012, originally named StormDB

Current release

10.17.1.0, November 2023

1.1, February 2017

10 R1, October 2018

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache version 2

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Mozilla public license

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

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS

Data scheme

yes

schema-free

yes

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 DML and DDL statements

yes

SQL-like query language (OQL)

yes

distributed, parallel query execution

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

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

Supported programming languages

Java

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

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

Server-side scripts

Stored procedures

Lua

Java Stored Procedures

user defined functions

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

fine grained access rights according to SQL-standard

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

JDBC tutorial: Easy installation and setup with Apache Derby
20 December 2019, TheServerSide.com

The Arrival of Java 20
21 March 2023, blogs.oracle.com

Installing Apache Hive 3.1.2 on Windows 10 | by Hadi Fadlallah
3 May 2020, Towards Data Science

The Apache® Software Foundation Announces 18 Years of Open Source Leadership
28 March 2017, GlobeNewswire

Payara Foundation Releases Payara Server 5 and Payara Micro 5
30 March 2018, InfoQ.com

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

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

Share this page