DBMS > Apache Pinot vs. Faircom DB vs. SQLite vs. Trafodion

System Properties Comparison Apache Pinot vs. Faircom DB vs. SQLite vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Realtime distributed OLAP datastore, designed to answer OLAP queries with low latency

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

Widely used embeddable, in-process RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

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

Score	0.35
Rank	#274	Overall
	#128	Relational DBMS

Score	0.18
Rank	#314	Overall
	#45	Key-value stores
	#141	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

pinot.apache.org

www.faircom.com/products/faircom-db

www.sqlite.org

trafodion.apache.org

Technical documentation

docs.pinot.apache.org

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

www.sqlite.org/docs.html

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation and contributors

FairCom Corporation

Dwayne Richard Hipp

Apache Software Foundation, originally developed by HP

Initial release

2015

1979

2000

2014

Current release

1.0.0, September 2023

V13, July 2024

3.46.1 (13 August 2024), August 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Restricted, free version available

Open Source

Public Domain

Open Source

Apache 2.0

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

Java

ANSI C, C++

C++, Java

Server operating systems

All OS with a Java JDK11 or higher

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

easily portable to other OSs

server-less

Linux

Data scheme

yes

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

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes, ANSI SQL with proprietary extensions

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC

Supported programming languages

Go
Java
Python

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

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding

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

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

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

yes

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

fine grained access rights according to SQL-standard

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.