DBMS > Faircom DB vs. jBASE vs. OpenQM vs. SQLite

System Properties Comparison Faircom DB vs. jBASE vs. OpenQM 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.

A robust multi-value DBMS comprising development tools and middleware

QpenQM is a high-performance, self-tuning, multi-value DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Relational DBMS

Multivalue DBMS

Relational DBMS

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

Score	0.24
Rank	#311	Overall
	#44	Key-value stores
	#140	Relational DBMS

Score	1.43
Rank	#160	Overall
	#3	Multivalue DBMS

Score	0.33
Rank	#286	Overall
	#10	Multivalue DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

www.faircom.com/products/faircom-db

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.sqlite.org

Technical documentation

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

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

www.sqlite.org/docs.html

Developer

FairCom Corporation

Rocket Software (formerly Zumasys)

Rocket Software, originally Martin Phillips

Dwayne Richard Hipp

Initial release

1979

1991

1993

2000

Current release

V12, November 2020

5.7

3.4-12

3.45.2 (12 March 2024), March 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

GPLv2, extended commercial license available

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

Server operating systems

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

easily portable to other OSs

AIX
Linux
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

server-less

Data scheme

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

schema-free

yes

with some exceptions

yes

dynamic column types

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

optional

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

Embedded SQL for jBASE in BASIC

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

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

.Net
Basic
Jabbascript
Java

.Net
Basic
C
Java
Objective C
PHP
Python

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

yes

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

yes

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

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

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

Access rights can be defined down to the item level

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.