DBMS > etcd vs. Firebird vs. Memcached vs. Snowflake vs. Transwarp Hippo

System Properties Comparison etcd vs. Firebird vs. Memcached vs. Snowflake vs. Transwarp Hippo

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

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

In-memory key-value store, originally intended for caching

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

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

Primary database model

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

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

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.05
Rank	#386	Overall
	#14	Vector DBMS

Website

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

www.firebirdsql.org

www.memcached.org

www.snowflake.com

www.transwarp.cn/en/subproduct/hippo

Technical documentation

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

www.firebirdsql.org/en/reference-manuals

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

Developer

Firebird Foundation

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

Initial release

2000

As fork of Borland's InterBase

2003

2014

2023

Current release

3.4, August 2019

5.0.0, January 2024

1.6.27, May 2024

1.0, May 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Initial Developer's Public License

Open Source

BSD license

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

C and C++

C++

Server operating systems

FreeBSD
Linux
Windows

experimental

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

gRPC
JSON over HTTP

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

Proprietary protocol

CLI Client
JDBC
ODBC

RESTful HTTP API

Supported programming languages

.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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C++
Java
Python

Server-side scripts

Stored procedures

PSQL

user defined functions

Triggers

yes, watching key changes

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

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

Users with fine-grained authorization concept

yes

using SASL (Simple Authentication and Security Layer) protocol

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

Role based access control and fine grained access rights

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.