DBMS > Bangdb vs. GridDB vs. Percona Server for MongoDB

System Properties Comparison Bangdb vs. GridDB vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

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

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Document store
Graph DBMS
Time Series DBMS

Time Series DBMS

Document store

Secondary database models

Spatial DBMS

Key-value store
Relational DBMS

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

Score	0.06
Rank	#353	Overall
	#48	Document stores
	#36	Graph DBMS
	#35	Time Series DBMS

Score	1.90
Rank	#123	Overall
	#10	Time Series DBMS

Score	0.47
Rank	#252	Overall
	#39	Document stores

Website

bangdb.com

griddb.net

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

docs.bangdb.com

docs.griddb.net

docs.percona.com/percona-distribution-for-mongodb

Developer

Sachin Sinha, BangDB

Toshiba Corporation

Percona

Initial release

2012

2013

2015

Current release

BangDB 2.0, October 2021

5.1, August 2022

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

BSD 3

Open Source

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

Open Source

GPL Version 2

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, C++

C++

Server operating systems

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

yes

numerical, string, blob, geometry, boolean, timestamp

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.

Secondary indexes

yes

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

Proprietary protocol
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

proprietary protocol using JSON

Supported programming languages

C
C#
C++
Java
Python

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

JavaScript

Triggers

yes, Notifications (with Streaming only)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

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

Tunable consistency, set CAP knob accordingly

Immediate consistency within container, eventual consistency across containers

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

ACID at container level

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

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

yes, run db with in-memory only mode

yes

via In-Memory Engine

User concepts

Access control

yes (enterprise version only)

Access rights for users can be defined per database

Access rights for users and roles

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

Recent citations in the news

Toshiba launches cloudy managed IoT database service running its own GridDB
8 April 2021, The Register

| TOSHIBA DIGITAL SOLUTIONS CORPORATION
30 October 2020, global.toshiba

Amazon Proposes to Develop New Data Center Campus in Virginia
26 August 2022, w.media

provided by Google News

MongoDB Performance Tuning
9 October 2024, Database Trends and Applications

5 Reasons to Run MongoDB on Kubernetes
6 March 2024, The New Stack

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

Is database-as-a-service in Percona’s future?
23 May 2022, VentureBeat

How to Plan Your MongoDB Upgrade
29 January 2024, The New Stack

provided by Google News

Share this page