DBMS > HEAVY.AI vs. JaguarDB vs. Kinetica vs. OpenSearch

System Properties Comparison HEAVY.AI vs. JaguarDB vs. Kinetica vs. OpenSearch

Please select another system to include it in the comparison.

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

Performant, highly scalable DBMS for AI and IoT applications

Fully vectorized database across both GPUs and CPUs

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Search engine

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series DBMS

Vector DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

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

www.jaguardb.com

www.kinetica.com

github.com/opensearch-project
opensearch.org

Technical documentation

docs.heavy.ai

www.jaguardb.com/support.html

docs.kinetica.com

opensearch.org/docs/latest

Developer

HEAVY.AI, Inc.

DataJaguar, Inc.

Kinetica

Amazon Web Services

Initial release

2016

2015

2012

2021

Current release

5.10, January 2022

3.3 July 2023

7.1, August 2021

2.5.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL V3.0

commercial

Open Source

Apache 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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

C++ and CUDA

C++

the server part. Clients available in other languages

C, C++

Java

Server operating systems

Linux

All OS with a Java VM

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

Typing

predefined data types such as float or date

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

All search fields are automatically indexed

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

JDBC
ODBC
Thrift
Vega

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

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

C++
Java
JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

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

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

yes

Transaction concepts

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

Concurrency

Support for concurrent manipulation of data

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

rights management via user accounts

Access rights for users and roles on table level

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.