DBMS > BigObject vs. Geode vs. Machbase Neo vs. Postgres-XL

System Properties Comparison BigObject vs. Geode vs. Machbase Neo 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

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

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

Time Series DBMS

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	#342	Overall
	#150	Relational DBMS

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.22
Rank	#324	Overall
	#29	Time Series DBMS

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Website

Technical documentation

docs.bigobject.io

geode.apache.org/docs

machbase.com/dbms

www.postgres-xl.org/documentation

Developer

BigObject, Inc.

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

Machbase

Initial release

2015

2002

2013

2014

since 2012, originally named StormDB

Current release

1.1, February 2017

V8.0, August 2023

10 R1, October 2018

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free test version available

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
Windows

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

SQL-like query language (OQL)

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

Supported programming languages

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

Server-side scripts

Stored procedures

Lua

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

Multi-source replication

selectable replication factor

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

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

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

volatile and lookup table

User concepts

Access control

Access rights per client and object definable

simple password-based access control

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

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

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

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

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

provided by Google News

“Luxembourg is a perfect target area”: Korean accelerator exec
27 October 2022, Delano.lu

provided by Google News

Share this page