DBMS > HEAVY.AI vs. Lovefield vs. RavenDB vs. YottaDB

System Properties Comparison HEAVY.AI vs. Lovefield vs. RavenDB vs. YottaDB

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

Embeddable relational database for web apps written in pure JavaScript

Open Source Operational and Transactional Enterprise NoSQL Document Database

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Document store

Key-value store

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Relational DBMS

using the Octo plugin

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

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	0.21
Rank	#309	Overall
	#43	Key-value stores

Website

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

google.github.io/lovefield

ravendb.net

yottadb.com

Technical documentation

docs.heavy.ai

github.com/google/lovefield/blob/master/docs/spec_index.md

ravendb.net/docs

yottadb.com/resources/documentation

Developer

HEAVY.AI, Inc.

Google

Hibernating Rhinos

YottaDB, LLC

Initial release

2016

2014

2010

2001

Current release

5.10, January 2022

2.1.12, February 2017

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license available

Open Source

AGPL 3.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++ and CUDA

JavaScript

Server operating systems

Linux

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

tested with Chrome, Firefox, IE, Safari

Linux
macOS
Raspberry Pi
Windows

Docker
Linux

Data scheme

yes

schema-free

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

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

SQL-like query language (RQL)

by using the Octo plugin

APIs and other access methods

JDBC
ODBC
Thrift
Vega

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

Users and groups based on OS-security mechanisms

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Dr. Mike Flaxman, VP or Product Management at HEAVY.AI – Interview Series
19 September 2024, Unite.AI

5 Q’s for Mike Flaxman, Vice President of Heavy.AI
15 August 2024, Center for Data Innovation

HEAVY.AI Accelerates Big Data Analytics with Vultr's High-Performance GPU Cloud Infrastructure
11 September 2024, insideBIGDATA

HEAVY.AI Accelerates Big Data Analytics with Vultr’s High-Performance GPU Cloud Infrastructure
11 September 2024, insideBIGDATA

Meta delivers strong earnings, but weak guidance and heavy AI spending prompt investors to bail
24 April 2024, SiliconANGLE News

provided by Google News

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and Accelerate Growth
13 June 2023, PR Newswire

Get To Know: Oren Eini, CEO, RavenDB
22 October 2019, Intelligent CIO

RavenDB Adds Graph Queries
15 May 2019, Datanami

provided by Google News

Share this page