DBMS > AlaSQL vs. Infobright vs. Kinetica vs. SQLite

System Properties Comparison AlaSQL vs. Infobright vs. Kinetica vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

Fully vectorized database across both GPUs and CPUs

Widely used embeddable, in-process RDBMS

Primary database model

Document 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.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

alasql.org

ignitetech.com/softwarelibrary/infobrightdb

www.kinetica.com

www.sqlite.org

Technical documentation

github.com/AlaSQL/alasql

docs.kinetica.com

www.sqlite.org/docs.html

Developer

Andrey Gershun & Mathias R. Wulff

Ignite Technologies Inc.; formerly InfoBright Inc.

Kinetica

Dwayne Richard Hipp

Initial release

2014

2005

2012

2000

Current release

7.1, August 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

MIT-License

commercial

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

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

JavaScript

C, C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

Linux
Windows

Linux

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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.

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

JavaScript API

ADO.NET
JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

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

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

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

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

exploiting MySQL or PostgreSQL frontend capabilities

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.