DBMS > Graph Engine vs. HEAVY.AI vs. Lovefield vs. Microsoft SQL Server vs. Prometheus

System Properties Comparison Graph Engine vs. HEAVY.AI vs. Lovefield vs. Microsoft SQL Server vs. Prometheus

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Microsofts flagship relational DBMS

Open-source Time Series DBMS and monitoring system

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

www.graphengine.io

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

google.github.io/lovefield

www.microsoft.com/en-us/sql-server

prometheus.io

Technical documentation

www.graphengine.io/docs/manual

docs.heavy.ai

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

learn.microsoft.com/en-US/sql/sql-server

prometheus.io/docs

Developer

Microsoft

HEAVY.AI, Inc.

Google

Microsoft

Initial release

2010

2016

2014

1989

2015

Current release

5.10, January 2022

2.1.12, February 2017

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Apache 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

.NET and C

C++ and CUDA

JavaScript

C++

Server operating systems

.NET

Linux

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

tested with Chrome, Firefox, IE, Safari

Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

RESTful HTTP/JSON API

Supported programming languages

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

yes

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Round robin

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes, but depending on the SQL-Server Edition

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.