DBMS > Databricks vs. GridGain vs. JanusGraph vs. Oracle vs. Sphinx

System Properties Comparison Databricks vs. GridGain vs. JanusGraph vs. Oracle vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Widely used RDBMS

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

Primary database model

Document store
Relational DBMS

Key-value store
Relational DBMS

Graph DBMS

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	81.08
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

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

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.databricks.com

www.gridgain.com

janusgraph.org

www.oracle.com/database

sphinxsearch.com

Technical documentation

docs.databricks.com

www.gridgain.com/docs/index.html

docs.janusgraph.org

docs.oracle.com/en/database

sphinxsearch.com/docs

Developer

Databricks

GridGain Systems, Inc.

Linux Foundation; originally developed as Titan by Aurelius

Oracle

Sphinx Technologies Inc.

Initial release

2013

2007

2017

1980

2001

Current release

GridGain 8.5.1

0.6.3, February 2023

23c, September 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, C++, .Net

Java

C and C++

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

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

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

Flexible Schema (defined schema, partial schema, 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

with Databricks 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

JDBC
ODBC
RESTful HTTP API

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Proprietary protocol

Supported programming languages

Python
R
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

Clojure
Java
Python

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

user defined functions and aggregates

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

yes

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

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

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

yes (replicated cache)

yes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

via Faunus, a graph analytics engine

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

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

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

User authentification and security via Rexster Graph Server

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.