DBMS > Kinetica vs. OrigoDB vs. Quasardb vs. SQLite

System Properties Comparison Kinetica vs. OrigoDB vs. Quasardb vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fully vectorized database across both GPUs and CPUs

A fully ACID in-memory object graph database

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Time Series 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.42
Rank	#261	Overall
	#120	Relational DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	0.13
Rank	#332	Overall
	#28	Time Series DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

docs.kinetica.com

origodb.com/docs

doc.quasar.ai/master

www.sqlite.org/docs.html

Developer

Kinetica

Robert Friberg et al

quasardb

Dwayne Richard Hipp

Initial release

2012

2009

under the name LiveDB

2009

2000

Current release

7.1, August 2021

3.14.1, January 2024

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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++

C++

Server operating systems

Linux

Linux
Windows

BSD
Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

integer and binary

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.

can be achieved using .NET

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

.Net

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

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

yes

Triggers

yes

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

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Write ahead log

yes

by using LevelDB

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

Transient mode

yes

User concepts

Access control

Access rights for users and roles on table level

Role based authorization

Cryptographically strong user authentication and audit trail

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.