DBMS > Apache Druid vs. GraphDB vs. Splunk vs. SQLite

System Properties Comparison Apache Druid vs. GraphDB vs. Splunk vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Enterprise-ready RDF and graph database with efficient reasoning, cluster and external index synchronization support. It supports also SQL JDBC access to Knowledge Graph and GraphQL over SPARQL.

Analytics Platform for Big Data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Graph DBMS
RDF store

Search engine

Relational DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	3.25
Rank	#91	Overall
	#7	Graph DBMS
	#4	RDF stores

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

druid.apache.org/docs/latest/design

graphdb.ontotext.com/documentation

docs.splunk.com/Documentation/Splunk

www.sqlite.org/docs.html

Social network pages

Developer

Apache Software Foundation and contributors

Ontotext

Splunk Inc.

Dwayne Richard Hipp

Initial release

2012

2000

2003

2000

Current release

29.0.1, April 2024

10.4, October 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Some plugins of GraphDB Workbench are open sourced

commercial

Limited free edition and free developer edition available

Open Source

Public Domain

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

Server operating systems

Linux
OS X
Unix

All OS with a Java VM
Linux
OS X
Windows

Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

schema-less columns are supported

schema-free and OWL/RDFS-schema support; RDF shapes

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes, supports real-time synchronization and indexing in SOLR/Elastic search/Lucene and GeoSPARQL geometry data indexes

yes

SQL

Support of SQL

SQL for querying

stored SPARQL accessed as SQL using Apache Calcite through JDBC/ODBC

Splunk Search Processing Language for search commands

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
RESTful HTTP/JSON API

GeoSPARQL
GraphQL
GraphQL Federation
Java API
JDBC
RDF4J API
RDFS
RIO
Sail API
Sesame REST HTTP Protocol
SPARQL 1.1

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C#
Clojure
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C#
Java
JavaScript
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

well-defined plugin interfaces; JavaScript server-side extensibility

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency, Eventual consistency (configurable in cluster mode per master or individual client request)

Eventual Consistency

Foreign keys

Referential integrity

yes

Constraint checking

yes

Transaction concepts

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

ACID

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

via file-system locks

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Default Basic authentication through RDF4J client, or via Java when run with cURL, default token-based in the Workbench or via Rest API, optional access through OpenID or Kerberos single sign-on.

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

Ontotext GraphDB is a semantic database engine that allows organizations to build...
» more

Competitive advantages

GraphDB allows you to link text and data in big knowledge graphs. It’s easy to experiment...
» more

Typical application scenarios

Metadata enrichment and management, linked data publishing, semantic inferencing...
» more

Key customers

GraphDB provides a platform for building next-generation AI and Knowledge Graph...
» more

Market metrics

GraphDB is the most utilized semantic triplestore for mission-critical enterprise...
» more

Licensing and pricing models

GraphDB Free is a non-commercial version and is free to use. GraphDB Enterprise edition...
» more

News

Riding the Databricks Wave with Hybrid Knowledge Graphs
6 June 2024

Matching Skills and Candidates with Graph RAG
31 May 2024

A Triple Store RAG Retriever
29 May 2024

Integrating GraphDB with Relational Database Systems
23 May 2024

Understanding the Graph Center of Excellence
17 May 2024

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.