DBMS > Apache Pinot vs. Graph Engine vs. HEAVY.AI vs. Microsoft SQL Server vs. Qdrant

System Properties Comparison Apache Pinot vs. Graph Engine vs. HEAVY.AI vs. Microsoft SQL Server vs. Qdrant

Editorial information provided by DB-Engines

Name

Description

Realtime distributed OLAP datastore, designed to answer OLAP queries with low latency

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

Microsofts flagship relational DBMS

A high-performance vector database with neural network or semantic-based matching

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Vector 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.38
Rank	#275	Overall
	#126	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Website

pinot.apache.org

www.graphengine.io

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

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

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.pinot.apache.org

www.graphengine.io/docs/manual

docs.heavy.ai

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

qdrant.tech/documentation

Developer

Apache Software Foundation and contributors

Microsoft

HEAVY.AI, Inc.

Microsoft

Qdrant

Initial release

2015

2010

2016

1989

2021

Current release

1.0.0, September 2023

5.10, January 2022

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

MIT License

Open Source

Apache Version 2; enterprise edition available

commercial

restricted free version is available

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

.NET and C

C++ and CUDA

C++

Rust

Server operating systems

All OS with a Java JDK11 or higher

.NET

Linux

Linux
Windows

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

Go
Java
Python

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC/Thrift
Python

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

yes

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Round robin

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

yes, but depending on the SQL-Server Edition

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable 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

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

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

Key-based authentication

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.