DBMS > GridGain vs. Percona Server for MongoDB vs. SQLite vs. SurrealDB

System Properties Comparison GridGain vs. Percona Server for MongoDB vs. SQLite vs. SurrealDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Widely used embeddable, in-process RDBMS

A fully ACID transactional, developer-friendly, multi-model DBMS

Primary database model

Key-value store
Relational DBMS

Document store

Relational DBMS

Document store
Graph DBMS

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

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

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.02
Rank	#190	Overall
	#33	Document stores
	#18	Graph DBMS

Website

www.gridgain.com

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

www.sqlite.org

surrealdb.com

Technical documentation

www.gridgain.com/docs/index.html

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

www.sqlite.org/docs.html

surrealdb.com/docs

Developer

GridGain Systems, Inc.

Percona

Dwayne Richard Hipp

SurrealDB Ltd

Initial release

2007

2015

2000

2022

Current release

GridGain 8.5.1

3.4.10-2.10, November 2017

3.46.0 (23 May 2024), May 2024

v1.5.0, May 2024

License

Commercial or Open Source

commercial

Open Source

GPL Version 2

Open Source

Public Domain

Open Source

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

Java, C++, .Net

C++

Rust

Server operating systems

Linux
OS X
Solaris
Windows

Linux

server-less

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

SQL-like query language

APIs and other access methods

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

proprietary protocol using JSON

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

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

JavaScript

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
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

via file-system locks

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.

yes

via In-Memory Engine

yes

User concepts

Access control

Security Hooks for custom implementations

Access rights for users and roles

yes, based on authentication and database rules

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.