DBMS > GridGain vs. Memcached vs. Oracle vs. Sphinx

System Properties Comparison GridGain vs. Memcached vs. Oracle vs. Sphinx

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

In-memory key-value store, originally intended for caching

Widely used RDBMS

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Search engine

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	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.gridgain.com

www.memcached.org

www.oracle.com/database

sphinxsearch.com

Technical documentation

www.gridgain.com/docs/index.html

github.com/memcached/memcached/wiki

docs.oracle.com/en/database

sphinxsearch.com/docs

Developer

GridGain Systems, Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

Sphinx Technologies Inc.

Initial release

2007

2003

1980

2001

Current release

GridGain 8.5.1

1.6.27, May 2024

23c, September 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence 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++

Server operating systems

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Unix
Windows

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

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

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

full-text index on all search fields

SQL

Support of SQL

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

yes

with proprietary extensions

SQL-like query language (SphinxQL)

APIs and other access methods

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

Proprietary protocol

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Proprietary protocol

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

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

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

none

Sharding, horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

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

yes

using SASL (Simple Authentication and Security Layer) protocol

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.