DBMS > Apache Drill vs. FeatureBase vs. Microsoft Azure Cosmos DB vs. Spark SQL

System Properties Comparison Apache Drill vs. FeatureBase vs. Microsoft Azure Cosmos DB vs. Spark SQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Real-time database platform that powers real-time analytics and machine learning applications by simultaneously executing low-latency, high-throughput, and highly concurrent workloads.

Globally distributed, horizontally scalable, multi-model database service

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.22
Rank	#309	Overall
	#139	Relational DBMS

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

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

drill.apache.org

www.featurebase.com

azure.microsoft.com/services/cosmos-db

spark.apache.org/sql

Technical documentation

drill.apache.org/docs

docs.featurebase.com

learn.microsoft.com/azure/cosmos-db

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Apache Software Foundation

Molecula and Pilosa Open Source Contributors

Microsoft

Apache Software Foundation

Initial release

2012

2017

2014

Current release

1.20.3, January 2023

2022, May 2022

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache Version 2

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

Scala

Server operating systems

Linux
OS X
Windows

Linux
macOS

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

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 SELECT statement is SQL:2003 compliant

SQL queries

SQL-like query language

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

gRPC
JDBC
Kafka Connector
ODBC

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

JDBC
ODBC

Supported programming languages

C++

Java
Python

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

Java
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes, using Linux fsync

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Access rights can be defined down to the item level

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.