DBMS > Elasticsearch vs. Qdrant vs. SiriDB vs. SQLite vs. Yaacomo

System Properties Comparison Elasticsearch vs. Qdrant vs. SiriDB vs. SQLite vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

Open Source Time Series DBMS

Widely used embeddable, in-process RDBMS

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.elastic.co/elasticsearch

github.com/qdrant/qdrant
qdrant.tech

siridb.com

www.sqlite.org

yaacomo.com

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

qdrant.tech/documentation

docs.siridb.com

www.sqlite.org/docs.html

Developer

Elastic

Qdrant

Cesbit

Dwayne Richard Hipp

Q2WEB GmbH

Initial release

2010

2021

2017

2000

2009

Current release

8.6, January 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Elastic License

Open Source

Apache Version 2.0

Open Source

MIT License

Open Source

Public Domain

commercial

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

Java

Rust

Server operating systems

All OS with a Java VM

Docker
Linux
macOS
Windows

Linux

server-less

Android
Linux
Windows

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

yes

Numeric data

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

All search fields are automatically indexed

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Collection-level replication

yes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency, tunable consistency

Immediate 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

via file-system locks

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.

Memcached and Redis integration

yes

User concepts

Access control

Key-based authentication

simple rights management via user accounts

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.