DBMS > Databend vs. Interbase vs. PostGIS vs. Snowflake

System Properties Comparison Databend vs. Interbase vs. PostGIS vs. Snowflake

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

Light-weight proven RDBMS

originally from Borland

Spatial extension of PostgreSQL

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.34
Rank	#283	Overall
	#130	Relational DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

www.embarcadero.com/products/interbase

postgis.net

www.snowflake.com

Technical documentation

docs.databend.com

docs.embarcadero.com/products/interbase

postgis.net/documentation

docs.snowflake.net/manuals/index.html

Developer

Databend Labs

Embarcadero

Snowflake Computing Inc.

Initial release

2021

1984

2005

2014

Current release

1.0.59, April 2023

InterBase 2020, December 2019

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL v2.0

commercial

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

Rust

Server operating systems

hosted
Linux
macOS

Android
iOS
Linux
OS X
Windows

hosted

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

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.

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Interbase Change Views

yes

based on PostgreSQL

yes

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

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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

Users with fine-grained authorization concept, user roles

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

Users with fine-grained authorization concept, user roles and pluggable authentication

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.