DBMS > Faircom DB vs. Stardog vs. Tarantool vs. Yanza

System Properties Comparison Faircom DB vs. Stardog vs. Tarantool vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. 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.

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Time Series DBMS for IoT Applications

Primary database model

Key-value store
Relational DBMS

Graph DBMS
RDF store

Document store
Key-value store
Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

www.faircom.com/products/faircom-db

www.stardog.com

www.tarantool.io

yanza.com

Technical documentation

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

docs.stardog.com

www.tarantool.io/en/doc

Developer

FairCom Corporation

Stardog-Union

Yanza

Initial release

1979

2010

2008

2015

Current release

V12, November 2020

7.3.0, May 2020

2.10.0, May 2022

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

ANSI C, C++

Java

C and C++

Server operating systems

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

easily portable to other OSs

Linux
macOS
Windows

BSD
Linux
macOS

Windows

Data scheme

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

schema-free and OWL/RDFS-schema support

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

Full-featured ANSI SQL support

APIs and other access methods

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

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Open binary protocol

HTTP API

Supported programming languages

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

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions and aggregates, HTTP Server extensions in Java

Lua, C and SQL stored procedures

Triggers

yes

via event handlers

yes, before/after data modification events, on replication events, client session events

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

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

Multi-source replication in HA-Cluster

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency in HA-Cluster

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

Access rights for users and roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.

Related products and services

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

More resources

DB-Engines blog posts

Data processing speed and reliability: in-memory synchronous replication
9 November 2021, Vladimir Perepelytsya, Tarantool (sponsor)

show all

Recent citations in the news

FairCom kicks off new era of database technology USA - English
10 November 2020, PR Newswire

provided by Google News

TaranHouse: New Big Data Warehouse Announced by Tarantool
4 April 2018, Newswire

Deploying Tarantool Cartridge applications with zero effort (Part 1)
16 December 2019, Хабр

Deploying Tarantool Cartridge applications with zero effort (Part 2)
13 April 2020, Хабр

Тarantool Cartridge: Sharding Lua Backend in Three Lines
9 October 2019, Хабр

VShard — horizontal scaling in Tarantool
7 March 2019, Хабр

provided by Google News

Share this page