DBMS > Amazon Redshift vs. BaseX vs. Faircom DB vs. ToroDB

System Properties Comparison Amazon Redshift vs. BaseX vs. Faircom DB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

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.

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Native XML DBMS

Key-value store
Relational DBMS

Document store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	1.56
Rank	#141	Overall
	#4	Native XML DBMS

Score	0.18
Rank	#314	Overall
	#45	Key-value stores
	#141	Relational DBMS

Website

aws.amazon.com/redshift

basex.org

www.faircom.com/products/faircom-db

github.com/torodb/server

Technical documentation

docs.aws.amazon.com/redshift

docs.basex.org

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

Developer

Amazon (based on PostgreSQL)

BaseX GmbH

FairCom Corporation

8Kdata

Initial release

2012

2007

1979

2016

Current release

11.2, August 2024

V13, July 2024

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

Restricted, free version available

Open Source

AGPL-V3

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

ANSI C, C++

Java

Server operating systems

hosted

Linux
OS X
Windows

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

easily portable to other OSs

All OS with a Java 7 VM

Data scheme

yes

schema-free

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

schema-free

Typing

predefined data types such as float or date

yes

XQuery supports types

yes, ANSI SQL Types, JSON, typed binary structures

yes

string, integer, double, boolean, date, object_id

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes, ANSI SQL with proprietary extensions

APIs and other access methods

JDBC
ODBC

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

Supported programming languages

All languages supporting JDBC/ODBC

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

.Net, JavaScript, C/C++

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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).

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

multiple readers, single writer

tunable from ACID to Eventually Consistent

Concurrency

Support for concurrent manipulation of data

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept on 4 levels

Fine grained access rights according to SQL-standard with additional protections for files

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.