DBMS > Cachelot.io vs. GeoMesa vs. Google Cloud Bigtable vs. Hazelcast

System Properties Comparison Cachelot.io vs. GeoMesa vs. Google Cloud Bigtable vs. Hazelcast

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

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.

A widely adopted in-memory data grid

Primary database model

Key-value store

Spatial DBMS

Key-value store
Wide column store

Key-value store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.04
Rank	#388	Overall
	#62	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Website

cachelot.io

www.geomesa.org

cloud.google.com/bigtable

hazelcast.com

Technical documentation

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

cloud.google.com/bigtable/docs

hazelcast.org/imdg/docs

Developer

CCRi and others

Google

Hazelcast

Initial release

2015

2014

2015

2008

Current release

5.0.0, May 2024

5.3.6, November 2023

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2; commercial licenses available

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

C++

Scala

Java

Server operating systems

FreeBSD
Linux
OS X

hosted

All OS with a Java VM

Data scheme

schema-free

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

Memcached protocol

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

JCache
JPA
Memcached protocol
RESTful HTTP API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

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

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

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

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

yes

Replicated Map

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

Transaction concepts

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

Atomic single-row operations

one or two-phase-commit; repeatable reads; read commited

Concurrency

Support for concurrent manipulation of data

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

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

Role-based access control

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

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

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

Google scales up Cloud Bigtable NoSQL database
27 January 2022, TechTarget

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

Google Cloud makes it cheaper to run smaller workloads on Bigtable
7 April 2020, TechCrunch

provided by Google News

Hazelcast appoints Anthony Griffin as Chief Architect -
11 June 2024, Enterprise Times

Hazelcast Weaves Wider Logic Threads Through The Data Fabric
7 March 2024, Forbes

Hazelcast 5.4 real time data processing platform boosts AI and consistency
17 April 2024, VentureBeat

Hazelcast Showcases Real-Time Data Platform at 2024 Gartner Summit
15 May 2024, Datanami

Real-Time Data Platform Hazelcast Introduces New Chief Technology Officer Adrian Soars
7 November 2023, Finovate

provided by Google News

Share this page