DBMS > Databend vs. GeoMesa vs. IBM Db2 vs. SQLite

System Properties Comparison Databend vs. GeoMesa vs. IBM Db2 vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Common in IBM host environments, 2 different versions for host and Windows/Linux

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	0.34
Rank	#283	Overall
	#130	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

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

www.geomesa.org

www.ibm.com/products/db2

www.sqlite.org

Technical documentation

docs.databend.com

www.geomesa.org/documentation/stable/user/index.html

www.ibm.com/docs/en/db2

www.sqlite.org/docs.html

Developer

Databend Labs

CCRi and others

IBM

Dwayne Richard Hipp

Initial release

2021

2014

1983

host version

2000

Current release

1.0.59, April 2023

5.0.0, May 2024

12.1, October 2016

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

commercial

free version is 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

Rust

Scala

C and C++

Server operating systems

hosted
Linux
macOS

AIX
HP-UX
Linux
Solaris
Windows
z/OS

server-less

Data scheme

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

SQL-92 is not fully supported

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

only with Windows/Unix/Linux Version

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes

with separate tools (MQ, InfoSphere)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

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

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

Users with fine-grained authorization concept, user roles

yes

depending on the DBMS used for storage

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.