DBMS > CockroachDB vs. Qdrant vs. SQLite vs. TigerGraph

System Properties Comparison CockroachDB vs. Qdrant vs. SQLite vs. TigerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

Widely used embeddable, in-process RDBMS

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

www.cockroachlabs.com

github.com/qdrant/qdrant
qdrant.tech

www.sqlite.org

www.tigergraph.com

Technical documentation

www.cockroachlabs.com/docs

qdrant.tech/documentation

www.sqlite.org/docs.html

docs.tigergraph.com

Developer

Cockroach Labs

Qdrant

Dwayne Richard Hipp

Initial release

2015

2021

2000

2017

Current release

24.1.0, May 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

Apache Version 2.0

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

Rust

C++

Server operating systems

Linux
macOS
Windows

Docker
Linux
macOS
Windows

server-less

Linux

Data scheme

dynamic schema

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

SQL-92 is not fully supported

SQL-like query language (GSQL)

APIs and other access methods

JDBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

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

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

C++
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Collection-level replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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.

yes

User concepts

Access control

Role-based access control

Key-based authentication

Role-based access control

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.