DBMS > 4D vs. MarkLogic vs. Splunk vs. SQLite

System Properties Comparison 4D vs. MarkLogic vs. Splunk vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Operational and transactional Enterprise NoSQL database

Analytics Platform for Big Data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Search engine

Relational DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.4d.com

www.progress.com/marklogic

www.splunk.com

www.sqlite.org

Technical documentation

developer.4d.com

www.progress.com/marklogic/documentation

docs.splunk.com/Documentation/Splunk

www.sqlite.org/docs.html

Developer

4D, Inc

MarkLogic Corp.

Splunk Inc.

Dwayne Richard Hipp

Initial release

1984

2001

2003

2000

Current release

v20, April 2023

11.0, December 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

restricted free version is 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

C++

Server operating systems

OS X
Windows

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

schema-free

Schema can be enforced

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

SQL92

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

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

4D proprietary IDE
PHP

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

via XQuery or JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

can act as a resource manager in an XA/JTA transaction

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, with Range Indexes

yes

User concepts

Access control

Users and groups

Role-based access control at the document and subdocument levels

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.