DBMS > Infobright vs. mSQL vs. OpenQM vs. SQLite vs. TerminusDB

System Properties Comparison Infobright vs. mSQL vs. OpenQM vs. SQLite vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

mSQL (Mini SQL) is a simple and lightweight RDBMS

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

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
RDF store

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

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

hughestech.com.au/products/msql

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

www.sqlite.org

terminusdb.com

Technical documentation

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Hughes Technologies

Rocket Software, originally Martin Phillips

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2005

1994

1993

2000

2018

Current release

4.4, October 2021

3.4-12

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

free licenses can be provided

Open Source

GPLv2, extended commercial license available

Open Source

Public Domain

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

server-less

Linux

Data scheme

yes

with some exceptions

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

yes

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Delphi
Java
Perl
PHP
Tcl

.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

JavaScript
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

exploiting MySQL or PostgreSQL frontend capabilities

Access rights can be defined down to the item level

Role-based access control

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.