DBMS > Apache Impala vs. Geode vs. OrigoDB vs. TerarkDB

System Properties Comparison Apache Impala vs. Geode vs. OrigoDB vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

A fully ACID in-memory object graph database

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

Key-value store

Document store
Object oriented DBMS

Key-value store

Secondary database models

Document store

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

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

impala.apache.org

geode.apache.org

origodb.com

github.com/bytedance/terarkdb

Technical documentation

impala.apache.org/impala-docs.html

geode.apache.org/docs

origodb.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

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

Robert Friberg et al

ByteDance, originally Terark

Initial release

2013

2002

2009

under the name LiveDB

2016

Current release

4.1.0, June 2022

1.1, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

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

C++

Java

C++

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language (OQL)

APIs and other access methods

JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net

C++
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

yes

Triggers

yes

Cache Event Listeners

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

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 for users, groups and roles

based on Apache Sentry and Kerberos

Access rights per client and object definable

Role based authorization

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 Impala 4 Supports Operator Multi-Threading
29 July 2021, iProgrammer

Apache Impala becomes Top-Level Project
28 November 2017, SDTimes.com

Cloudera Bringing Impala to AWS Cloud
28 November 2017, Datanami

Hudi: Uber Engineering’s Incremental Processing Framework on Apache Hadoop
12 March 2017, Uber

Updates & Upserts in Hadoop Ecosystem with Apache Kudu
27 October 2017, KDnuggets

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

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

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

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

HPE acquires Ampool to gain distributed SQL engine
9 July 2021, VentureBeat

provided by Google News

Share this page