DBMS > HEAVY.AI vs. Ignite vs. Linter vs. SiteWhere vs. SQLite

System Properties Comparison HEAVY.AI vs. Ignite vs. Linter vs. SiteWhere vs. SQLite

Editorial information provided by DB-Engines

Name

Description

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

RDBMS for high security requirements

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/heavyai/heavydb
www.heavy.ai

ignite.apache.org

linter.ru

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

docs.heavy.ai

apacheignite.readme.io/docs

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

HEAVY.AI, Inc.

Apache Software Foundation

relex.ru

SiteWhere

Dwayne Richard Hipp

Initial release

2016

2015

1990

2010

2000

Current release

5.10, January 2022

Apache Ignite 2.6

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

commercial

Open Source

Common Public Attribution License Version 1.0

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

C++, Java, .Net

C and C++

Java

Server operating systems

Linux

Linux
OS X
Solaris
Windows

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

Linux
OS X
Windows

server-less

Data scheme

yes

predefined scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
Thrift
Vega

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C#
C++
Java
PHP
Python
Ruby
Scala

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

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

yes (compute grid and cache interceptors can be used instead)

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

none

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes (replicated cache)

Source-replica replication

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

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

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.