DBMS > RavenDB vs. SAP SQL Anywhere vs. SQLite vs. XTDB

System Properties Comparison RavenDB vs. SAP SQL Anywhere vs. SQLite vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open Source Operational and Transactional Enterprise NoSQL Document Database

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Widely used embeddable, in-process RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store

Relational DBMS

Document store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

ravendb.net

www.sap.com/products/technology-platform/sql-anywhere.html

www.sqlite.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

ravendb.net/docs

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

www.xtdb.com/docs

Developer

Hibernating Rhinos

SAP

formerly Sybase

Dwayne Richard Hipp

Juxt Ltd.

Initial release

2010

1992

2000

2019

Current release

5.4, July 2022

17, July 2015

3.46.0 (23 May 2024), May 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

AGPL version 3, commercial license available

commercial

Open Source

Public Domain

Open Source

MIT License

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

Clojure

Server operating systems

Linux
macOS
Raspberry Pi
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes, extensible-data-notation format

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

SQL-like query language (RQL)

yes

SQL-92 is not fully supported

limited SQL, making use of Apache Calcite

APIs and other access methods

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP REST
JDBC

Supported programming languages

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
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

Clojure
Java

Server-side scripts

Stored procedures

yes

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

Database mirroring

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

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.