DBMS > Graph Engine vs. Oracle vs. Splunk vs. TigerGraph

System Properties Comparison Graph Engine vs. Oracle vs. Splunk vs. TigerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Widely used RDBMS

Analytics Platform for Big Data

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Search engine

Graph 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	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

www.graphengine.io

www.oracle.com/database

www.splunk.com

www.tigergraph.com

Technical documentation

www.graphengine.io/docs/manual

docs.oracle.com/en/database

docs.splunk.com/Documentation/Splunk

docs.tigergraph.com

Developer

Microsoft

Oracle

Splunk Inc.

Initial release

2010

1980

2003

2017

Current release

23c, September 2023

License

Commercial or Open Source

Open Source

MIT License

commercial

restricted free version is available

commercial

Limited free edition and free developer edition available

commercial

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

.NET and C

C and C++

C++

Server operating systems

.NET

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

Linux
OS X
Solaris
Windows

Linux

Data scheme

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

SQL

Support of SQL

yes

with proprietary extensions

Splunk Search Processing Language for search commands

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

C#
C++
F#
Visual Basic

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#
Java
JavaScript
PHP
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

yes

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

isolation level can be parameterized

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

fine grained access rights according to SQL-standard

Access rights for users and roles

Role-based access control

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.