DBMS > BaseX vs. FoundationDB vs. Snowflake vs. Splunk

System Properties Comparison BaseX vs. FoundationDB vs. Snowflake vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

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

Ordered key-value store. Core features are complimented by layers.

Cloud-based data warehousing service for structured and semi-structured data

Analytics Platform for Big Data

Primary database model

Native XML DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Search engine

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

basex.org

github.com/apple/foundationdb

www.snowflake.com

www.splunk.com

Technical documentation

docs.basex.org

apple.github.io/foundationdb

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

BaseX GmbH

FoundationDB

Snowflake Computing Inc.

Splunk Inc.

Initial release

2007

2013

2014

2003

Current release

11.0, June 2024

6.2.28, November 2020

License

Commercial or Open Source

Open Source

BSD license

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

some layers support schemas

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

XQuery supports types

some layers support typing

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

supported in specific SQL layer only

yes

Splunk Search Processing Language for search commands

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

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

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

in SQL-layer only

user defined functions

yes

Triggers

yes

via events

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

in SQL-layer only

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

Concurrency

Support for concurrent manipulation of data

yes

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.

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

Users with fine-grained authorization concept, user roles and pluggable authentication

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.