DBMS > Faircom DB vs. ObjectBox vs. Tkrzw vs. Trafodion

System Properties Comparison Faircom DB vs. ObjectBox vs. Tkrzw vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Lightweight, fast on-device database for IoT, Mobile and Embedded devices, persisting and synchronising objects and vectors

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Transactional SQL-on-Hadoop DBMS

Primary database model

Key-value store
Relational DBMS

Object oriented DBMS
Vector DBMS

Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

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

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

Score	1.08
Rank	#179	Overall
	#6	Object oriented DBMS
	#9	Vector DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

www.faircom.com/products/faircom-db

github.com/objectbox
objectbox.io

dbmx.net/tkrzw

trafodion.apache.org

Technical documentation

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

docs.objectbox.io

trafodion.apache.org/documentation.html

Developer

FairCom Corporation

ObjectBox Limited

Mikio Hirabayashi

Apache Software Foundation, originally developed by HP

Initial release

1979

2017

2020

2014

Current release

V13, July 2024

4.0 (May 2024)

0.9.3, August 2020

2.3.0, February 2019

License

Commercial or Open Source

commercial

Restricted, free version available

Bindings are released under Apache 2.0

Apache License 2.0

Open Source

Apache Version 2.0

Open Source

Apache 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

ANSI C, C++

C and C++

C++

C++, Java

Server operating systems

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

easily portable to other OSs

Android
Any POSIX system
Docker
iOS
Linux
macOS
QNX
Windows

Linux
macOS

Linux

Data scheme

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes, plus "flex" map-like types

yes

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

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Proprietary native API

ADO.NET
JDBC
ODBC

Supported programming languages

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

C
C++
Dart (Flutter)
Go
Java
Kotlin
Python
Swift

C++
Java
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Data sync between devices allowing occasional connected databases to work completely offline

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

using specific database classes

User concepts

Access control

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

yes

fine grained access rights according to SQL-standard

More information provided by the system vendor

News

MongoDB Realm & Device Sync alternatives – ObjectBox
17 September 2024

Local AI – what it is and why we need it
11 September 2024

First on-device Vector Database (aka Semantic Index) for iOS
24 July 2024

Retrieval Augmented Generation (RAG) with vector databases: Expanding AI Capabilities
18 June 2024

The on-device Vector Database for Android and Java
29 May 2024

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