DBMS > Apache Druid vs. EJDB vs. Google BigQuery vs. SwayDB vs. Typesense

System Properties Comparison Apache Druid vs. EJDB vs. Google BigQuery vs. SwayDB vs. Typesense

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Large scale data warehouse service with append-only tables

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Relational DBMS
Time Series DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Score	0.79
Rank	#210	Overall
	#14	Search engines

Website

druid.apache.org

github.com/Softmotions/ejdb

cloud.google.com/bigquery

swaydb.simer.au

typesense.org

Technical documentation

druid.apache.org/docs/latest/design

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/bigquery/docs

typesense.org/docs

Developer

Apache Software Foundation and contributors

Softmotions

Google

Simer Plaha

Initial release

2012

2010

2018

2015

Current release

29.0.1, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

GPLv2

commercial

Open Source

GNU Affero GPL V3.0

Open Source

GPL V3

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

Scala

C++

Server operating systems

Linux
OS X
Unix

server-less

hosted

Linux

Data scheme

yes

schema-less columns are supported

schema-free

yes

schema-free

pre-defined schema optional

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

SQL for querying

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

in-process shared library

RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Kotlin
Scala

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

Multi-source replication using RAFT

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Since BigQuery is designed for querying data

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.