DBMS > JaguarDB vs. Transbase vs. XTDB

System Properties Comparison JaguarDB vs. Transbase vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Performant, highly scalable DBMS for AI and IoT applications

A resource-optimized, high-performance, universally applicable RDBMS

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

Primary database model

Key-value store
Vector DBMS

Relational DBMS

Document store

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.jaguardb.com

www.transaction.de/en/products/transbase.html

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

Technical documentation

www.jaguardb.com/support.html

www.transaction.de/en/products/transbase/features.html

www.xtdb.com/docs

Developer

DataJaguar, Inc.

Transaction Software GmbH

Juxt Ltd.

Initial release

2015

1987

2019

Current release

3.3 July 2023

Transbase 8.3, 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

GPL V3.0

commercial

free development license

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

C++

the server part. Clients available in other languages

C and C++

Clojure

Server operating systems

Linux

FreeBSD
Linux
macOS
Solaris
Windows

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

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

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.

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

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

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

rights management via user accounts

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

Share this page