DBMS > GridGain vs. Manticore Search vs. MySQL vs. Oracle

System Properties Comparison GridGain vs. Manticore Search vs. MySQL vs. Oracle

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

Multi-storage database for search, including full-text search.

Widely used open source RDBMS

Widely used RDBMS

Primary database model

Key-value store
Relational DBMS

Search engine

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

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	0.29
Rank	#302	Overall
	#21	Search engines

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Website

www.gridgain.com

manticoresearch.com

www.mysql.com

www.oracle.com/database

Technical documentation

www.gridgain.com/docs/index.html

manual.manticoresearch.com

dev.mysql.com/doc

docs.oracle.com/en/database

Developer

GridGain Systems, Inc.

Manticore Software

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

Initial release

2007

2017

1995

1980

Current release

GridGain 8.5.1

6.0, February 2023

8.4.0, April 2024

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted free version is 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java, C++, .Net

C++

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

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

Data scheme

yes

Fixed schema

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

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

SQL-like query language

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
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

Server-side scripts

Stored procedures

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

user defined functions

yes

proprietary syntax

PL/SQL

also stored procedures in Java possible

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

not for MyISAM storage engine

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.