DBMS > EventStoreDB vs. GridDB vs. MongoDB

System Properties Comparison EventStoreDB vs. GridDB vs. MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

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

Event Store

Time Series DBMS

Document store

Secondary database models

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	1.05
Rank	#181	Overall
	#1	Event Stores

Score	2.00
Rank	#114	Overall
	#9	Time Series DBMS

Score	402.51
Rank	#5	Overall
	#1	Document stores

Website

www.eventstore.com

griddb.net

www.mongodb.com

Technical documentation

developers.eventstore.com

docs.griddb.net

www.mongodb.com/docs/manual

Developer

Event Store Limited

Toshiba Corporation

MongoDB, Inc

Initial release

2012

2013

2009

Current release

21.2, February 2021

5.1, August 2022

7.0.5, January 2024

License

Commercial or Open Source

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.

Implementation language

C++

Server operating systems

Linux
Windows

Linux

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.

Secondary indexes

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

Read-only SQL queries via the MongoDB Atlas SQL Interface

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

Supported programming languages

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

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

JavaScript

Triggers

yes

in MongoDB Atlas only

Partitioning methods

Methods for storing different data on different nodes

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

Source-replica replication

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

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Immediate consistency within container, eventual consistency across containers

Eventual Consistency

can be individually decided for each read operation
Immediate Consistency

default behaviour

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

ACID at container level

Multi-document ACID Transactions with snapshot isolation

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional, enabled by default

In-memory capabilities

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

yes

In-memory storage engine introduced with MongoDB version 3.2

User concepts

Access control

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

Competitive advantages

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

Typical application scenarios

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

Key customers

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

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» 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.