DBMS > JaguarDB vs. Kinetica vs. SQLite vs. Titan

System Properties Comparison JaguarDB vs. Kinetica vs. SQLite vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Performant, highly scalable DBMS for AI and IoT applications

Fully vectorized database across both GPUs and CPUs

Widely used embeddable, in-process RDBMS

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Key-value store
Vector DBMS

Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.jaguardb.com

www.kinetica.com

www.sqlite.org

github.com/thinkaurelius/titan

Technical documentation

www.jaguardb.com/support.html

docs.kinetica.com

www.sqlite.org/docs.html

github.com/thinkaurelius/titan/wiki

Developer

DataJaguar, Inc.

Kinetica

Dwayne Richard Hipp

Aurelius, owned by DataStax

Initial release

2015

2012

2000

2012

Current release

3.3 July 2023

7.1, August 2021

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

GPL V3.0

commercial

Open Source

Public Domain

Open Source

Apache license, 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

C++

the server part. Clients available in other languages

C, C++

Java

Server operating systems

Linux

server-less

Linux
OS X
Unix
Windows

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

Clojure
Java
Python

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

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

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

rights management via user accounts

Access rights for users and roles on table level

User authentification and security via Rexster Graph Server

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.