DBMS > Dolt vs. Interbase vs. MySQL vs. Qdrant

System Properties Comparison Dolt vs. Interbase vs. MySQL vs. Qdrant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

Light-weight proven RDBMS

originally from Borland

Widely used open source RDBMS

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

Primary database model

Relational DBMS

Key/Value like access via memcached API

Vector DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.28
Rank	#167	Overall
	#7	Vector DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

www.embarcadero.com/products/interbase

www.mysql.com

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.dolthub.com

docs.embarcadero.com/products/interbase

dev.mysql.com/doc

qdrant.tech/documentation

Developer

DoltHub Inc

Embarcadero

Oracle

since 2010, originally MySQL AB, then Sun

Qdrant

Initial release

2018

1984

1995

2021

Current release

InterBase 2020, December 2019

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Rust

Server operating systems

Linux
macOS
Windows

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
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.

export as XML data possible

yes

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

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
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

Interbase procedure and trigger language

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Interbase Change Views

Multi-source replication
Source-replica replication

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

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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

Only one user is configurable, and must be specified in the config file at startup

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.