DBMS > GridGain vs. Sphinx vs. SQLite vs. Titan

System Properties Comparison GridGain vs. Sphinx vs. SQLite vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

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

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

Widely used embeddable, in-process RDBMS

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Key-value store
Relational DBMS

Search engine

Relational DBMS

Graph DBMS

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

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.gridgain.com

sphinxsearch.com

www.sqlite.org

github.com/thinkaurelius/titan

Technical documentation

www.gridgain.com/docs/index.html

sphinxsearch.com/docs

www.sqlite.org/docs.html

github.com/thinkaurelius/titan/wiki

Developer

GridGain Systems, Inc.

Sphinx Technologies Inc.

Dwayne Richard Hipp

Aurelius, owned by DataStax

Initial release

2007

2001

2000

2012

Current release

GridGain 8.5.1

3.5.1, February 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

Open Source

Apache license, version 2.0

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

Java

Server operating systems

Linux
OS X
Solaris
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Linux
OS X
Unix
Windows

Data scheme

yes

dynamic column types

yes

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

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 (SphinxQL)

yes

SQL-92 is not fully supported

APIs and other access methods

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

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

Clojure
Java
Python

Server-side scripts

Stored procedures

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

yes

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

none

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

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

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

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

In-memory capabilities

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

yes

User concepts

Access control

Security Hooks for custom implementations

User authentification and security via Rexster Graph Server

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.