DBMS > MySQL vs. Qdrant vs. SiteWhere vs. Transbase

System Properties Comparison MySQL vs. Qdrant vs. SiteWhere vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

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

M2M integration platform for persisting/querying time series data

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Vector DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.53
Rank	#145	Overall
	#7	Vector DBMS

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Score	0.05
Rank	#355	Overall
	#150	Relational DBMS

Website

www.mysql.com

github.com/qdrant/qdrant
qdrant.tech

github.com/sitewhere/sitewhere

www.transaction.de/en/products/transbase.html

Technical documentation

dev.mysql.com/doc

qdrant.tech/documentation

sitewhere1.sitewhere.io/index.html

www.transaction.de/en/products/transbase/features.html

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Qdrant

SiteWhere

Transaction Software GmbH

Initial release

1995

2021

2010

1987

Current release

9.0.0, July 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

Open Source

Common Public Attribution License Version 1.0

commercial

free development license

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 C++

Rust

Java

C and C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS
Windows

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

predefined scheme

yes

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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.

yes

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Collection-level replication

selectable replication factor

based on HBase

Source-replica 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

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

yes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Key-based authentication

Users with fine-grained authorization concept

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.