DBMS > Brytlyt vs. Faircom EDGE vs. Kinetica vs. SQLite

System Properties Comparison Brytlyt vs. Faircom EDGE vs. Kinetica vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Fully vectorized database across both GPUs and CPUs

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

brytlyt.io

www.faircom.com/products/faircom-edge

www.kinetica.com

www.sqlite.org

Technical documentation

docs.brytlyt.io

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

docs.kinetica.com

www.sqlite.org/docs.html

Developer

Brytlyt

FairCom Corporation

Kinetica

Dwayne Richard Hipp

Initial release

2016

1979

2012

2000

Current release

5.0, August 2023

V3, October 2020

7.1, August 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

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

C, C++ and CUDA

ANSI C, C++

C, C++

Server operating systems

Linux
OS X
Windows

Android
Linux

ARM, x86
Raspbian
Windows

Linux

server-less

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

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

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

C++
Java
JavaScript (Node.js)
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

user defined functions

in PL/pgSQL

yes

.Net, JavaScript, C/C++

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Synchronous and asynchronous realtime replication based on transaction logs

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

via file-system locks

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

GPU vRAM or System RAM

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Access rights for users and roles on table 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.