DBMS > Coveo vs. JSqlDb vs. Microsoft Azure Cosmos DB vs. QuestDB

System Properties Comparison Coveo vs. JSqlDb vs. Microsoft Azure Cosmos DB vs. QuestDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

JavaScript Query Language Database, stores JavaScript objects and primitives

Globally distributed, horizontally scalable, multi-model database service

A high performance open source SQL database for time series data

Primary database model

Search engine

Document store
Object oriented DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	2.14
Rank	#116	Overall
	#11	Search engines

Score	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.81
Rank	#98	Overall
	#7	Time Series DBMS

Website

www.coveo.com

jsqldb.org (offline)

azure.microsoft.com/services/cosmos-db

questdb.io

Technical documentation

docs.coveo.com

learn.microsoft.com/azure/cosmos-db

questdb.io/docs

Developer

Coveo

Konrad von Backstrom

Microsoft

QuestDB Technology Inc

Initial release

2012

2018

2014

Current release

0.8, December 2018

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

Apache 2.0

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 (Zero-GC), C++, Rust

Server operating systems

hosted

Linux
macOS
Windows

hosted

Linux
macOS
Windows

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

schema-free via InfluxDB Line Protocol

Typing

predefined data types such as float or date

yes

JSON types

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 properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

SQL with time-series extensions

APIs and other access methods

RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

Supported programming languages

C#
Java
JavaScript
Python

JavaScript

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Server-side scripts

Stored procedures

functions in JavaScript

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Implicit feature of the cloud service

Source-replica replication with eventual consistency

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

ACID for single-table writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using RocksDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

through memory mapped files

User concepts

Access control

granular access controls, API key management, content filters

Access rights can be defined down to the item level

More information provided by the system vendor

News

Combine Java and Rust Code Coverage in a Polyglot Project
10 September 2024

Building a new vector based storage model
22 August 2024

Calibrating VWAP executions with QuestDB and Grafana
16 August 2024

The story of our SAMPLE BY enhancements
7 August 2024

A cloud engineer's first QuestDB Pull Request
5 August 2024

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.