DBMS > GridGain vs. LMDB vs. Oracle vs. Prometheus vs. WakandaDB

System Properties Comparison GridGain vs. LMDB vs. Oracle vs. Prometheus vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

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

A high performant, light-weight, embedded key-value database library

Widely used RDBMS

Open-source Time Series DBMS and monitoring system

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Key-value store
Relational DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

www.gridgain.com

www.symas.com/symas-embedded-database-lmdb

www.oracle.com/database

prometheus.io

wakanda.github.io

Technical documentation

www.gridgain.com/docs/index.html

www.lmdb.tech/doc

docs.oracle.com/en/database

prometheus.io/docs

wakanda.github.io/doc

Developer

GridGain Systems, Inc.

Symas

Oracle

Wakanda SAS

Initial release

2007

2011

1980

2015

2012

Current release

GridGain 8.5.1

0.9.32, January 2024

23c, September 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

AGPLv3, extended commercial license available

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 and C++

C++, JavaScript

Server operating systems

Linux
OS X
Solaris
Windows

Linux
Unix
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

APIs and other access methods

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

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

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

Multi-source replication
Source-replica replication

yes

by Federation

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

yes

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.