DBMS > IBM Cloudant vs. JaguarDB vs. Qdrant vs. SQLite vs. Teradata

System Properties Comparison IBM Cloudant vs. JaguarDB vs. Qdrant vs. SQLite vs. Teradata

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Performant, highly scalable DBMS for AI and IoT applications

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

Widely used embeddable, in-process RDBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Document store

Key-value store
Vector DBMS

Vector DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

www.ibm.com/products/cloudant

www.jaguardb.com

github.com/qdrant/qdrant
qdrant.tech

www.sqlite.org

www.teradata.com

Technical documentation

cloud.ibm.com/docs/Cloudant

www.jaguardb.com/support.html

qdrant.tech/documentation

www.sqlite.org/docs.html

docs.teradata.com

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

DataJaguar, Inc.

Qdrant

Dwayne Richard Hipp

Teradata

Initial release

2010

2015

2021

2000

1984

Current release

3.3 July 2023

3.46.0 (23 May 2024), May 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

Apache Version 2.0

Open Source

Public Domain

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

Erlang

C++

the server part. Clients available in other languages

Rust

Server operating systems

hosted

Linux

Docker
Linux
macOS
Windows

server-less

hosted
Linux

Data scheme

schema-free

yes

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.

yes

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

SQL-92 is not fully supported

yes

SQL 2016 + extensions

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

.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
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

Collection-level replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

rights management via user accounts

Key-based authentication

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.