DBMS > Dolt vs. etcd vs. Firebird vs. SAP HANA

System Properties Comparison Dolt vs. etcd vs. Firebird vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

A distributed reliable key-value store

Firebird is an open source RDBMS forked from Borland's InterBase

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

etcd.io
github.com/etcd-io/etcd

www.firebirdsql.org

www.sap.com/products/hana.html

Technical documentation

docs.dolthub.com

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

www.firebirdsql.org/en/reference-manuals

help.sap.com/hana

Developer

DoltHub Inc

Firebird Foundation

SAP

Initial release

2018

2000

As fork of Borland's InterBase

2010

Current release

3.4, August 2019

5.0.0, January 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

Initial Developer's Public License

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
Windows

experimental

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
HTTP REST

gRPC
JSON over HTTP

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

currently in alpha release

PSQL

SQLScript, R

Triggers

yes

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Source-replica replication

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

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

Only one user is configurable, and must be specified in the config file at startup

Users with fine-grained authorization concept

yes

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.