DBMS > Geode vs. GeoMesa vs. Google Cloud Bigtable vs. NSDb

System Properties Comparison Geode vs. GeoMesa vs. Google Cloud Bigtable vs. NSDb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Key-value store

Spatial DBMS

Key-value store
Wide column store

Time Series DBMS

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

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

geode.apache.org

www.geomesa.org

cloud.google.com/bigtable

nsdb.io

Technical documentation

geode.apache.org/docs

www.geomesa.org/documentation/stable/user/index.html

cloud.google.com/bigtable/docs

nsdb.io/Architecture

Developer

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

CCRi and others

Google

Initial release

2002

2014

2015

2017

Current release

1.1, February 2017

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Scala

Java, Scala

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux
macOS

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

gRPC
HTTP REST
WebSocket

Supported programming languages

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

C#
C++
Go
Java
JavaScript (Node.js)
Python

Java
Scala

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

Internal replication in Colossus, and regional replication between two clusters in different zones

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

depending on storage layer

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

Atomic single-row operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

In-memory capabilities

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

yes

depending on storage layer

User concepts

Access control

Access rights per client and object definable

yes

depending on the DBMS used for storage

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

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

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, oreilly.com

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

provided by Google News

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

What is Google Bigtable? | Definition from TechTarget
1 March 2022, TechTarget

Google announces Axion, its first Arm-based CPU for data centers
9 April 2024, Yahoo Movies Canada

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Share this page