DBMS > Apache Drill vs. CrateDB vs. SAP SQL Anywhere vs. SQLite

System Properties Comparison Apache Drill vs. CrateDB vs. SAP SQL Anywhere vs. SQLite

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

Distributed Database based on Lucene

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	0.73
Rank	#229	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#8	Vector DBMS

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

cratedb.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.sqlite.org

Technical documentation

drill.apache.org/docs

cratedb.com/docs

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Crate

SAP

formerly Sybase

Dwayne Richard Hipp

Initial release

2012

2013

1992

2000

Current release

1.20.3, January 2023

17, July 2015

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

commercial

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

CrateDB Cloud: a distributed SQL database that spreads data and processing across an elastic cluster of shared nothing nodes. CrateDB Cloud enables data insights at scale on Microsoft Azure, AWS and Google Cloud Platform.

Implementation language

Java

Server operating systems

Linux
OS X
Windows

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

dynamic column types

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes, but no triggers and constraints, and PostgreSQL compatibility

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

user defined functions

user defined functions (Javascript)

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Configurable replication on table/partition-level

Source-replica replication

Database mirroring

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Read-after-write consistency on record level

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

Depending on the underlying data source

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

rights management via user accounts

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

The enterprise database for time series, documents, and vectors. Distributed - Native...
» more

Competitive advantages

Response time in milliseconds: e ven for complex ad-hoc queries. Massive scaling...
» more

Typical application scenarios

IoT: accelerate your IIoT projects with CrateDB, delivering real-time analytics...
» more

Key customers

Across all continents, CrateDB is used by companies of all sizes to meet the most...
» more

Market metrics

The CrateDB open source project was started in 2013 Honorable Mention in 2021 Gartner®...
» more

Licensing and pricing models

See CrateDB pricing >
» more

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.