DBMS > GeoMesa vs. Greenplum vs. GridDB vs. LokiJS vs. MongoDB

System Properties Comparison GeoMesa vs. Greenplum vs. GridDB vs. LokiJS vs. MongoDB

Editorial information provided by DB-Engines

Name

Description

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Scalable in-memory time series database optimized for IoT and Big Data

In-memory JavaScript DBMS

One of the most popular document stores available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Secondary database models

Document store
Spatial DBMS

Key-value store
Relational DBMS

Spatial DBMS
Search engine

integrated Lucene index, currently in MongoDB Atlas only.
Time Series DBMS

Time Series Collections introduced in Release 5.0
Vector DBMS

currently available in the MongoDB Atlas cloud service only

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	9.23
Rank	#47	Overall
	#30	Relational DBMS

Score	2.02
Rank	#132	Overall
	#11	Time Series DBMS

Score	0.48
Rank	#262	Overall
	#42	Document stores

Score	423.96
Rank	#5	Overall
	#1	Document stores

Website

www.geomesa.org

greenplum.org

griddb.net

github.com/techfort/LokiJS

www.mongodb.com

Technical documentation

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

docs.greenplum.org

docs.griddb.net

techfort.github.io/LokiJS

www.mongodb.com/docs/manual

Developer

CCRi and others

Pivotal Software Inc.

Toshiba Corporation

MongoDB, Inc

Initial release

2014

2005

2013

2014

2009

Current release

4.0.5, February 2024

7.0.0, September 2023

5.1, August 2022

6.0.7, June 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

MongoDB Inc.'s Server Side Public License v1. Prior versions were published under GNU AGPL v3.0. Commercial licenses are also available.

Cloud-based only

Only available as a cloud service

MongoDB available as DBaaS (MongoDB Atlas)

DBaaS offerings (sponsored links)

Database as a Service

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

MongoDB Atlas: Global multi-cloud database with unmatched data distribution and mobility across AWS, Azure, and Google Cloud, built-in automation for resource and workload optimization, and so much more.

Implementation language

Scala

C++

JavaScript

C++

Server operating systems

Linux

server-less, requires a JavaScript environment (browser, Node.js)

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

Although schema-free, documents of the same collection often follow the same structure. Optionally impose all or part of a schema by defining a JSON schema.

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

string, integer, double, decimal, boolean, date, object_id, geospatial

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

since Version 4.2

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

SQL92, SQL-like TQL (Toshiba Query Language)

Read-only SQL queries via the MongoDB Atlas SQL Interface

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JavaScript API

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

Supported programming languages

C
Java
Perl
Python
R

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript

Actionscript

unofficial driver
C
C#
C++
Clojure

unofficial driver
ColdFusion

unofficial driver
D

unofficial driver
Dart

unofficial driver
Delphi

unofficial driver
Erlang
Go
Groovy

unofficial driver
Haskell
Java
JavaScript
Kotlin
Lisp

unofficial driver
Lua

unofficial driver
MatLab

unofficial driver
Perl
PHP
PowerShell

unofficial driver
Prolog

unofficial driver
Python
R

unofficial driver
Ruby
Rust
Scala
Smalltalk

unofficial driver
Swift

Server-side scripts

Stored procedures

yes

View functions in JavaScript

JavaScript

Triggers

yes

in MongoDB Atlas only

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Sharding

Partitioned by hashed, ranged, or zoned sharding keys. Live resharding allows users to change their shard keys as an online operation with zero downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

none

Multi-Source deployments with MongoDB Atlas Global Clusters
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

none

Eventual Consistency

can be individually decided for each read operation
Immediate Consistency

default behaviour

Foreign keys

Referential integrity

yes

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

ACID

ACID at container level

atomic operations within a single collection possible

Multi-document ACID Transactions with snapshot isolation

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes

optional, enabled by default

In-memory capabilities

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

depending on storage layer

yes

In-memory storage engine introduced with MongoDB version 3.2

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

MongoDB provides an integrated suite of cloud database and data services to accelerate...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Built around the flexible document data model and unified API, MongoDB is a developer...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

AI-enriched intelligent apps (Continental, Telefonica, Iron Mountain) Internet of...
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

ADP, Adobe, Amadeus, AstraZeneca, Auto Trader, Barclays, BBVA, Bosch, Cisco, CERN,...
» more

Market metrics

GitHub trending repository
» more

Hundreds of millions downloads, over 150,000+ Atlas clusters provisioned every month...
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

MongoDB database server: Server-Side Public License (SSPL) . Commercial licenses...
» more

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.