DBMS > Faircom DB vs. Infobright vs. Postgres-XL vs. Vertica vs. XTDB

System Properties Comparison Faircom DB vs. Infobright vs. Postgres-XL vs. Vertica vs. XTDB

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.

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Column oriented

Document store

Secondary database models

Document store
Spatial DBMS

Spatial DBMS
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	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	0.43
Rank	#260	Overall
	#119	Relational DBMS

Score	9.62
Rank	#42	Overall
	#26	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

www.faircom.com/products/faircom-db

ignitetech.com/softwarelibrary/infobrightdb

www.postgres-xl.org

www.vertica.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

www.postgres-xl.org/documentation

vertica.com/documentation

www.xtdb.com/docs

Developer

FairCom Corporation

Ignite Technologies Inc.; formerly InfoBright Inc.

OpenText

previously Micro Focus and Hewlett Packard

Juxt Ltd.

Initial release

1979

2005

2014

since 2012, originally named StormDB

2005

2019

Current release

V13, July 2024

10 R1, October 2018

12.0.3, January 2023

1.19, September 2021

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

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

Open Source

Mozilla public license

commercial

Limited community edition free

Open Source

MIT License

Cloud-based only

Only available as a cloud service

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

ANSI C, C++

C++

Clojure

Server operating systems

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

easily portable to other OSs

Linux
Windows

Linux
macOS

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

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

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

yes, extensible-data-notation format

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

XML type, but no XML query functionality

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

No Indexes Required. Different internal optimization strategy, but same functionality included.

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

distributed, parallel query execution

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

limited SQL, making use of Apache Calcite

APIs and other access methods

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

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

HTTP REST
JDBC

Supported programming languages

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

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Clojure
Java

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

horizontal partitioning

horizontal partitioning, hierarchical partitioning

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

Source-replica replication

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Bi-directional Spark integration

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

MVCC

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

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

Recent citations in the news

Vertica on Kubernetes
20 June 2024, blogs.opentext.com

What’s New in OpenText Vertica
10 January 2024, blogs.opentext.com

Stonebraker Seeks to Invert the Computing Paradigm with DBOS
12 March 2024, Datanami

MapR Hadoop Upgrade Spins YARN, Supports HP Vertica Analytics Platform
31 May 2024, Data Center Knowledge

Querying a Vertica data source in Amazon Athena using the Athena Federated Query SDK
11 February 2021, AWS Blog

provided by Google News

Share this page