DBMS > Interbase vs. OrientDB vs. Qdrant vs. Snowflake

System Properties Comparison Interbase vs. OrientDB vs. Qdrant vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Light-weight proven RDBMS

originally from Borland

Multi-model DBMS (Document, Graph, Key/Value)

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store

Vector DBMS

Relational DBMS

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

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.embarcadero.com/products/interbase

orientdb.org

github.com/qdrant/qdrant
qdrant.tech

www.snowflake.com

Technical documentation

docs.embarcadero.com/products/interbase

www.orientdb.com/docs/last/index.html

qdrant.tech/documentation

docs.snowflake.net/manuals/index.html

Developer

Embarcadero

OrientDB LTD; CallidusCloud; SAP

Qdrant

Snowflake Computing Inc.

Initial release

1984

2010

2021

2014

Current release

InterBase 2020, December 2019

3.2.29, March 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Rust

Server operating systems

Android
iOS
Linux
OS X
Windows

All OS with a Java JDK (>= JDK 6)

Docker
Linux
macOS
Windows

hosted

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

export as XML data possible

yes

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

SQL-like query language, no joins

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

Java, Javascript

user defined functions

Triggers

yes

Hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

Multi-source replication

Collection-level replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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

fine grained access rights according to SQL-standard

Access rights for users and roles; record level security configurable

Key-based authentication

Users with fine-grained authorization concept, user roles and pluggable 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.