DBMS > 4D vs. Graph Engine vs. HEAVY.AI vs. Splunk vs. SQLite

System Properties Comparison 4D vs. Graph Engine vs. HEAVY.AI vs. Splunk vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Analytics Platform for Big Data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.4d.com

www.graphengine.io

github.com/heavyai/heavydb
www.heavy.ai

www.splunk.com

www.sqlite.org

Technical documentation

developer.4d.com

www.graphengine.io/docs/manual

docs.heavy.ai

docs.splunk.com/Documentation/Splunk

www.sqlite.org/docs.html

Developer

4D, Inc

Microsoft

HEAVY.AI, Inc.

Splunk Inc.

Dwayne Richard Hipp

Initial release

1984

2010

2016

2003

2000

Current release

v20, April 2023

5.10, January 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache Version 2; enterprise edition available

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

.NET and C

C++ and CUDA

Server operating systems

OS X
Windows

.NET

Linux

Linux
OS X
Solaris
Windows

server-less

Data scheme

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

SQL

Support of SQL

yes

close to SQL 92

yes

Splunk Search Processing Language for search commands

yes

SQL-92 is not fully supported

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

4D proprietary IDE
PHP

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC/Thrift
Python

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Round robin

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Eventual Consistency

Foreign keys

Referential integrity

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

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

User concepts

Access control

Users and groups

fine grained access rights according to SQL-standard

Access rights for users and roles

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.