DBMS > H2 vs. Interbase vs. Prometheus vs. Snowflake vs. XTDB

System Properties Comparison H2 vs. Interbase vs. Prometheus vs. Snowflake vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Light-weight proven RDBMS

originally from Borland

Open-source Time Series DBMS and monitoring system

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Spatial DBMS

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

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.h2database.com

www.embarcadero.com/products/interbase

prometheus.io

www.snowflake.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.h2database.com/html/main.html

docs.embarcadero.com/products/interbase

prometheus.io/docs

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

Thomas Mueller

Embarcadero

Snowflake Computing Inc.

Juxt Ltd.

Initial release

2005

1984

2015

2014

2019

Current release

2.2.220, July 2023

InterBase 2020, December 2019

1.19, September 2021

License

Commercial or Open Source

Open Source

dual-licence (Mozilla public license, Eclipse public license)

commercial

Open Source

Apache 2.0

commercial

Open Source

MIT License

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

Java

Clojure

Server operating systems

All OS with a Java VM

Android
iOS
Linux
OS X
Windows

Linux
Windows

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

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

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes

yes, extensible-data-notation format

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

Import of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

Java

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

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

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

With clustering: 2 database servers on different computers operate on identical copies of a database

Interbase Change Views

yes

by Federation

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.