DBMS > Oracle vs. Qdrant vs. Solr

System Properties Comparison Oracle vs. Qdrant vs. Solr

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS

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

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Relational DBMS

Vector DBMS

Search engine

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Spatial DBMS

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

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

www.oracle.com/database

github.com/qdrant/qdrant
qdrant.tech

solr.apache.org

Technical documentation

docs.oracle.com/en/database

qdrant.tech/documentation

solr.apache.org/resources.html

Developer

Oracle

Qdrant

Apache Software Foundation

Initial release

1980

2021

2006

Current release

23c, September 2023

9.6.0, April 2024

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache Version 2.0

Open Source

Apache Version 2

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

Server operating systems

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Docker
Linux
macOS
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

Schemaless in JSON and XML columns

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

Solr Parallel SQL Interface

APIs and other access methods

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Java API
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Collection-level replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

optimistic locking

Concurrency

Support for concurrent manipulation of data

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Key-based authentication

yes

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.