DBMS > Apache Drill vs. FatDB vs. Geode vs. Newts vs. TerarkDB

System Properties Comparison Apache Drill vs. FatDB vs. Geode vs. Newts vs. TerarkDB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Time Series DBMS based on Cassandra

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

Document store
Relational DBMS

Document store
Key-value store

Key-value store

Time Series DBMS

Key-value store

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

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

Website

drill.apache.org

geode.apache.org

opennms.github.io/newts

github.com/bytedance/terarkdb

Technical documentation

drill.apache.org/docs

geode.apache.org/docs

github.com/OpenNMS/newts/wiki

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

FatCloud

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

OpenNMS Group

ByteDance, originally Terark

Initial release

2012

2002

2014

2016

Current release

1.20.3, January 2023

1.1, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

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
OS X
Windows

Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Windows

Data scheme

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 SELECT statement is SQL:2003 compliant

Via inetgration in SQL Server

SQL-like query language (OQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST
Java API

C++ API
Java API

Supported programming languages

C++

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

Java

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes

via applications

user defined functions

Triggers

yes

via applications

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

selectable replication factor

based on Cassandra

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Can implement custom security layer via applications

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

Analyse Kafka messages with SQL queries using Apache Drill
23 September 2019, Towards Data Science

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Using Apache Iceberg for Developing Modern Data Tables
3 October 2023, Open Source For You

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

Apache Drill improves big data SQL query engine
31 August 2021, TechTarget

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

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

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

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Farewell, Froggy: The Age of Ribbit Is Nearing an End
25 May 2013, Mother Jones

provided by Google News

Share this page