DBMS > BaseX vs. CouchDB vs. OrientDB vs. SQLite

System Properties Comparison BaseX vs. CouchDB vs. OrientDB 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.

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Multi-model DBMS (Document, Graph, Key/Value)

Widely used embeddable, in-process RDBMS

Primary database model

Native XML DBMS

Document store

Document store
Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

docs.basex.org

docs.couchdb.org/en/stable

www.orientdb.com/docs/last/index.html

www.sqlite.org/docs.html

Developer

BaseX GmbH

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Initial release

2007

2005

2010

2000

Current release

10.7, August 2023

3.3.3, December 2023

3.2.29, March 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

BSD license

Open Source

Apache version 2

Open Source

Apache version 2

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

Erlang

Java

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java JDK (>= JDK 6)

server-less

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

dynamic column types

Typing

predefined data types such as float or date

XQuery supports 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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

RESTful HTTP/JSON API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

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#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

View functions in JavaScript

Java, Javascript

Triggers

yes

via events

yes

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

multiple readers, single writer

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights for users can be defined per database

Access rights for users and roles; record level security configurable

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.