DBMS > BigObject vs. Ehcache vs. Geode vs. TerarkDB

System Properties Comparison BigObject vs. Ehcache vs. Geode vs. TerarkDB

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

A widely adopted Java cache with tiered storage options

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

bigobject.io

www.ehcache.org

geode.apache.org

github.com/bytedance/terarkdb

Technical documentation

docs.bigobject.io

www.ehcache.org/documentation

geode.apache.org/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

BigObject, Inc.

Terracotta Inc, owned by Software AG

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

ByteDance, originally Terark

Initial release

2015

2009

2002

2016

Current release

3.10.0, March 2022

1.1, February 2017

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

restricted open source 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

Java

C++

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

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language (OQL)

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

JCache

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

Supported programming languages

Java

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

C++
Java

Server-side scripts

Stored procedures

Lua

user defined functions

Triggers

yes

Cache Event Listeners

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

by using Terracotta Server

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

Transaction concepts

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

yes

supports JTA and can work as an XA resource

yes, on a single node

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, DZone

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