DBMS > Faircom DB vs. Riak KV vs. SQLite

System Properties Comparison Faircom DB vs. Riak KV vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed, fault tolerant key-value store

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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

Score	0.53
Rank	#228	Overall
	#34	Key-value stores
	#111	Relational DBMS

Score	5.08
Rank	#66	Overall
	#9	Key-value stores

Score	125.06
Rank	#9	Overall
	#6	Relational DBMS

Website

www.faircom.com/products/faircom-db

riak.com/products/riak-kv

www.sqlite.org

Technical documentation

learn.faircomcorp.com/developers/documentation_directory

www.sqlite.org/docs.html

Developer

FairCom Corporation

Basho Technologies

Dwayne Richard Hipp

Initial release

1979

2009

2000

Current release

V12, November 2020

2.1.0, April 2015

3.35.4 (2 April 2021), April 2021

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache version 2, commercial enterprise edition

Open Source

Public Domain

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++

Erlang

Server operating systems

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

easily portable to other OSs

Linux
OS X

server-less

Data scheme

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

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

not rigid because of 'dynamic typing' concept.

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

restricted

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

SQL-92 is not fully supported

APIs and other access methods

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

HTTP API
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

JavaScript and Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

no "single point of failure"

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

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

via file-system locks

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

User concepts

Access control

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

More information provided by the system vendor

Specific characteristics

Achieve Hundreds of Thousands of Transactions Per Second on A Single Database Server...
» more

Competitive advantages

Top Features SQL Key-value store and navigational NoSQL API Indexed binary objects...
» more

Typical application scenarios

Real-time transaction processing solutions leverage FairCom DB because its NoSQL...
» more

Key customers

Microsoft, UPS, Verizon, Motorola, Commvault, Thomson Reuters, ACI, BNY Mellon, Rockwell...
» more

Market metrics

From banking and financial transactions, transportation, warehouse automation, package...
» more

Licensing and pricing models

Just as the technical aspects of FairCom DB are flexible to meet operation requirements,...
» more

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.