StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Databases
  5. GridDB vs MongoDB

GridDB vs MongoDB

OverviewDecisionsComparisonAlternatives

Overview

MongoDB
MongoDB
Stacks96.6K
Followers82.0K
Votes4.1K
GitHub Stars27.7K
Forks5.7K
GridDB
GridDB
Stacks3
Followers18
Votes0
GitHub Stars0
Forks0

GridDB vs MongoDB: What are the differences?

Introduction

GridDB and MongoDB are both popular NoSQL databases that offer different features and capabilities. While they share some similarities, there are key differences between the two that set them apart.

  1. Data Model: GridDB is a hybrid database that combines the functionalities of a key-value store and a relational database, allowing for more flexible data modeling. It supports tables with defined schemas and relationships between them. On the other hand, MongoDB is a document-oriented database, where data is stored in flexible, JSON-like documents without a predefined schema. This makes it more suitable for unstructured or semi-structured data.

  2. Scalability and Distribution: GridDB is designed for high-performance, high-concurrency, and large-scale data processing. It offers a distributed architecture that allows for horizontal scaling across multiple nodes, ensuring high availability and fault tolerance. MongoDB also offers scalability and distribution but lacks the automatic data partitioning capabilities of GridDB. It relies on sharding to distribute data across multiple servers manually.

  3. Consistency and Durability: GridDB provides ACID (Atomicity, Consistency, Isolation, Durability) transactions to ensure data consistency and durability. It offers both immediate and eventual consistency models, depending on the application requirements. MongoDB, on the other hand, provides only eventual consistency by default and requires additional configurations for achieving strong consistency.

  4. Query Language: GridDB uses a SQL-based query language called GridDB SQL, which allows for complex querying and data manipulation operations, including joins and aggregations. MongoDB uses its own query language called MongoDB Query Language (MQL), which offers similar functionality but with a different syntax. MQL supports rich query expressions and aggregation pipelines.

  5. Indexing Capabilities: GridDB offers a range of indexing options, including primary keys, secondary indexes, composite indexes, and bitmap indexes. These indexes can be used to optimize query performance and enable fast data retrieval. MongoDB also supports various types of indexes, including single-field, compound, multikey, geospatial, and text indexes. It provides flexible indexing options to cater to different data querying needs.

  6. Community and Ecosystem: MongoDB has a larger and more established community compared to GridDB. It has been widely adopted and has a rich ecosystem of tools, libraries, and third-party integrations. GridDB is relatively newer and has a smaller user base and ecosystem. However, it is actively developed and supported by its parent company, which ensures regular updates and improvements.

In summary, GridDB offers a hybrid data model, advanced scalability and distribution features, ACID transactions, SQL-based querying, flexible indexing capabilities, and a growing ecosystem. MongoDB, on the other hand, provides a document-oriented data model, scalability and distribution options, eventual consistency, MongoDB Query Language, various indexing options, and a mature community and ecosystem.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on MongoDB, GridDB

George
George

Student

Mar 18, 2020

Needs adviceonPostgreSQLPostgreSQLPythonPythonDjangoDjango

Hello everyone,

Well, I want to build a large-scale project, but I do not know which ORDBMS to choose. The app should handle real-time operations, not chatting, but things like future scheduling or reminders. It should be also really secure, fast and easy to use. And last but not least, should I use them both. I mean PostgreSQL with Python / Django and MongoDB with Node.js? Or would it be better to use PostgreSQL with Node.js?

*The project is going to use React for the front-end and GraphQL is going to be used for the API.

Thank you all. Any answer or advice would be really helpful!

620k views620k
Comments
Ido
Ido

Mar 6, 2020

Decided

My data was inherently hierarchical, but there was not enough content in each level of the hierarchy to justify a relational DB (SQL) with a one-to-many approach. It was also far easier to share data between the frontend (Angular), backend (Node.js) and DB (MongoDB) as they all pass around JSON natively. This allowed me to skip the translation layer from relational to hierarchical. You do need to think about correct indexes in MongoDB, and make sure the objects have finite size. For instance, an object in your DB shouldn't have a property which is an array that grows over time, without limit. In addition, I did use MySQL for other types of data, such as a catalog of products which (a) has a lot of data, (b) flat and not hierarchical, (c) needed very fast queries.

575k views575k
Comments
Mike
Mike

Mar 20, 2020

Needs advice

We Have thousands of .pdf docs generated from the same form but with lots of variability. We need to extract data from open text and more important - from tables inside the docs. The output of Couchbase/Mongo will be one row per document for backend processing. ADOBE renders the tables in an unusable form.

241k views241k
Comments

Detailed Comparison

MongoDB
MongoDB
GridDB
GridDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

It is a highly scalable, in-memory NoSQL time series database optimized for IoT and Big Data. It has a KVS (Key-Value Store)-type data model that is suitable for sensor data stored in a timeseries. It is a database that can be easily scaled-out according to the number of sensors.

Flexible data model, expressive query language, secondary indexes, replication, auto-sharding, in-place updates, aggregation, GridFS
IoT Data Model; Distributed; Horizontal Scalability;In-memory;Hybrid Cluster Management;Fast Ingest;Composite Indexes;Petabyte-Scale DB size;Time series functions;Geometry data support
Statistics
GitHub Stars
27.7K
GitHub Stars
0
GitHub Forks
5.7K
GitHub Forks
0
Stacks
96.6K
Stacks
3
Followers
82.0K
Followers
18
Votes
4.1K
Votes
0
Pros & Cons
Pros
  • 829
    Document-oriented storage
  • 594
    No sql
  • 554
    Ease of use
  • 465
    Fast
  • 410
    High performance
Cons
  • 6
    Very slowly for connected models that require joins
  • 3
    Not acid compliant
  • 2
    Proprietary query language
No community feedback yet
Integrations
No integrations available
Python
Python
Ubuntu
Ubuntu
Node.js
Node.js
CentOS
CentOS
Fluentd
Fluentd
openSUSE
openSUSE

What are some alternatives to MongoDB, GridDB?

Redis

Redis

Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.

MySQL

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase