DBMS > BaseX vs. Faircom DB vs. SQLite vs. VictoriaMetrics

System Properties Comparison BaseX vs. Faircom DB vs. SQLite vs. VictoriaMetrics

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.

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Widely used embeddable, in-process RDBMS

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Native XML DBMS

Key-value store
Relational DBMS

Relational DBMS

Time Series 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.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Website

basex.org

www.faircom.com/products/faircom-db

www.sqlite.org

victoriametrics.com

Technical documentation

docs.basex.org

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

www.sqlite.org/docs.html

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

BaseX GmbH

FairCom Corporation

Dwayne Richard Hipp

VictoriaMetrics

Initial release

2007

1979

2000

2018

Current release

11.0, June 2024

V12, November 2020

3.46.0 (23 May 2024), May 2024

v1.91, May 2023

License

Commercial or Open Source

Open Source

BSD license

commercial

Restricted, free version available

Open Source

Public Domain

Open Source

Apache Version 2.0

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

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

server-less

FreeBSD
Linux
macOS
OpenBSD

Data scheme

schema-free

schema free, schema optional, schema required, partial schema,

yes

dynamic column types

Typing

predefined data types such as float or date

XQuery supports types

yes, ANSI SQL Types, JSON, typed binary structures

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.

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

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
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

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

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

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++

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

none

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

multiple readers, single writer

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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 access rights according to SQL-standard with additional protections for files

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.