DBMS > GeoMesa vs. GridGain vs. LMDB vs. Snowflake

System Properties Comparison GeoMesa vs. GridGain vs. LMDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

GridGain is an in-memory computing platform, built on Apache Ignite

A high performant, light-weight, embedded key-value database library

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Spatial DBMS

Key-value store
Relational DBMS

Key-value store

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.geomesa.org

www.gridgain.com

www.symas.com/symas-embedded-database-lmdb

www.snowflake.com

Technical documentation

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

www.gridgain.com/docs/index.html

www.lmdb.tech/doc

docs.snowflake.net/manuals/index.html

Developer

CCRi and others

GridGain Systems, Inc.

Symas

Snowflake Computing Inc.

Initial release

2014

2007

2011

2014

Current release

5.0.0, May 2024

GridGain 8.5.1

0.9.32, January 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

commercial

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

Scala

Java, C++, .Net

Server operating systems

Linux
OS X
Solaris
Windows

Linux
Unix
Windows

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes (replicated cache)

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

Security Hooks for custom implementations

Users with fine-grained authorization concept, user roles and pluggable authentication

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.