DBMS > Apache Druid vs. Coveo vs. NSDb vs. SQL.JS vs. SQLite

System Properties Comparison Apache Druid vs. Coveo vs. NSDb vs. SQL.JS vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Port of SQLite to JavaScript

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Search engine

Time Series DBMS

Relational DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

druid.apache.org/docs/latest/design

docs.coveo.com

nsdb.io/Architecture

sql.js.org/documentation/index.html

www.sqlite.org/docs.html

Developer

Apache Software Foundation and contributors

Coveo

Alon Zakai

enhancements implemented by others

Dwayne Richard Hipp

Initial release

2012

2017

2012

2000

Current release

29.0.1, April 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

Apache Version 2.0

Open Source

Public Domain

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

Java, Scala

JavaScript

Server operating systems

Linux
OS X
Unix

hosted

Linux
macOS

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Data scheme

yes

schema-less columns are supported

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

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

yes

not rigid because of 'dynamic typing' concept.

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 fields are automatically indexed

yes

SQL

Support of SQL

SQL for querying

SQL-like query language

yes

SQL-92 is not fully supported

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
RESTful HTTP/JSON API

RESTful HTTP API

gRPC
HTTP REST
WebSocket

JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
Java
JavaScript
Python

Java
Scala

JavaScript

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Using Apache Lucene

except by serializing a db to a file

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

granular access controls, API key management, content filters

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.