DBMS > EsgynDB vs. GeoMesa vs. Google Cloud Bigtable vs. KeyDB

System Properties Comparison EsgynDB vs. GeoMesa vs. Google Cloud Bigtable vs. KeyDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Primary database model

Relational DBMS

Spatial DBMS

Key-value store
Wide column store

Key-value store

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

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

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Website

www.esgyn.cn

www.geomesa.org

cloud.google.com/bigtable

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

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

cloud.google.com/bigtable/docs

docs.keydb.dev

Developer

Esgyn

CCRi and others

Google

EQ Alpha Technology Ltd.

Initial release

2015

2014

2015

2019

Current release

5.0.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

BSD-3

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++, Java

Scala

C++

Server operating systems

Linux

hosted

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

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

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

Java Stored Procedures

Lua

Triggers

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 between multi datacenters

depending on storage layer

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

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

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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

simple password-based access control and ACL

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 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

Google introduces Cloud Bigtable managed NoSQL database to process data at scale
6 May 2015, VentureBeat

provided by Google News

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

Share this page