DBMS > CrateDB vs. Databend vs. HEAVY.AI vs. SQLite

System Properties Comparison CrateDB vs. Databend vs. HEAVY.AI vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Database based on Lucene

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	0.69
Rank	#226	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#11	Vector DBMS

Score	0.28
Rank	#287	Overall
	#131	Relational DBMS

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

cratedb.com

github.com/datafuselabs/databend
www.databend.com

github.com/heavyai/heavydb
www.heavy.ai

www.sqlite.org

Technical documentation

cratedb.com/docs

docs.databend.com

docs.heavy.ai

www.sqlite.org/docs.html

Developer

Crate

Databend Labs

HEAVY.AI, Inc.

Dwayne Richard Hipp

Initial release

2013

2021

2016

2000

Current release

5.8.1, August 2024

1.0.59, April 2023

5.10, January 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; enterprise edition available

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.

Implementation language

Java

Rust

C++ and CUDA

Server operating systems

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

hosted
Linux
macOS

Linux

server-less

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

yes, but no triggers and constraints, and PostgreSQL compatibility

yes

SQL-92 is not fully supported

APIs and other access methods

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

CLI Client
JDBC
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.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

Go
Java
JavaScript (Node.js)
Python
Rust

All languages supporting JDBC/ODBC/Thrift
Python

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 (Javascript)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Round robin

none

Replication methods

Methods for redundantly storing data on multiple nodes

Configurable replication on table/partition-level

none

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

rights management via user accounts

Users with fine-grained authorization concept, user roles

fine grained access rights according to SQL-standard

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.