DBMS > Faircom DB vs. Linter vs. MySQL vs. Trino

System Properties Comparison Faircom DB vs. Linter vs. MySQL vs. Trino

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.

RDBMS for high security requirements

Widely used open source RDBMS

Fast distributed SQL query engine for big data analytics. Forked from Presto and originally named PrestoSQL

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

Document store
Key-value store
Spatial DBMS
Search engine
Time Series DBMS
Wide column store

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.03
Rank	#368	Overall
	#156	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	5.28
Rank	#61	Overall
	#35	Relational DBMS

Website

www.faircom.com/products/faircom-db

linter.ru

www.mysql.com

trino.io

Technical documentation

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

dev.mysql.com/doc

trino.io/broadcast
trino.io/docs/current

Developer

FairCom Corporation

relex.ru

Oracle

since 2010, originally MySQL AB, then Sun

Trino Software Foundation

Initial release

1979

1990

1995

2012

2020 rebranded from PrestoSQL

Current release

V13, July 2024

9.0.0, July 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 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

ANSI C, C++

C and C++

Java

Server operating systems

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

easily portable to other OSs

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

for devlopment

Data scheme

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

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

yes

depending on connected data-source

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

with proprietary extensions

yes

APIs and other access methods

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

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
RESTful HTTP API
Trino CLI

Supported programming languages

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

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Go
Java
JavaScript (Node.js)
Python
R
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

proprietary syntax

yes, depending on connected data-source

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

depending on connected data-source

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
Source-replica replication

depending on connected data-source

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

depending on connected data-source

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

not for MyISAM storage engine

depending on connected data-source

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

yes

depending on connected data-source

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

Users with fine-grained authorization concept

no user groups or roles

SQL standard access control

More information provided by the system vendor

News

23 is a go, keeping pace with Java
17 September 2024

65: Performance boosts
12 September 2024

64: Control with Open Policy Agent OPA
22 August 2024

63: Querying with JS
1 August 2024

62: A lakehouse that simply works at Prezi
11 July 2024

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.