DBMS > BaseX vs. Faircom EDGE vs. Splunk vs. SQLite

System Properties Comparison BaseX vs. Faircom EDGE vs. Splunk vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Analytics Platform for Big Data

Widely used embeddable, in-process RDBMS

Primary database model

Native XML DBMS

Key-value store
Relational DBMS

Search engine

Relational DBMS

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

basex.org

www.faircom.com/products/faircom-edge

www.splunk.com

www.sqlite.org

Technical documentation

docs.basex.org

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

docs.splunk.com/Documentation/Splunk

www.sqlite.org/docs.html

Developer

BaseX GmbH

FairCom Corporation

Splunk Inc.

Dwayne Richard Hipp

Initial release

2007

1979

2003

2000

Current release

11.0, June 2024

V3, October 2020

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

BSD license

commercial

Restricted, free version 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

Java

ANSI C, C++

Server operating systems

Linux
OS X
Windows

Android
Linux

ARM, x86
Raspbian
Windows

Linux
OS X
Solaris
Windows

server-less

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

dynamic column types

Typing

predefined data types such as float or date

XQuery supports types

yes, ANSI Standard SQL Types

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

ANSI SQL queries

Splunk Search Processing Language for search commands

yes

SQL-92 is not fully supported

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

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

.Net, JavaScript, C/C++

yes

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning

Customizable business rules for partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Synchronous and asynchronous realtime replication based on transaction logs

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
Tunable Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

multiple readers, single writer

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

across SQL and NoSQL

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

Users with fine-grained authorization concept on 4 levels

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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.