DBMS > etcd vs. Interbase vs. KeyDB vs. Snowflake

System Properties Comparison etcd vs. Interbase vs. KeyDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

Light-weight proven RDBMS

originally from Borland

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

Primary database model

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

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

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.embarcadero.com/products/interbase

github.com/Snapchat/KeyDB
keydb.dev

www.snowflake.com

Technical documentation

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

docs.embarcadero.com/products/interbase

docs.keydb.dev

docs.snowflake.net/manuals/index.html

Developer

Embarcadero

EQ Alpha Technology Ltd.

Snowflake Computing Inc.

Initial release

1984

2019

2014

Current release

3.4, August 2019

InterBase 2020, December 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

BSD-3

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++

Server operating systems

FreeBSD
Linux
Windows

experimental

Android
iOS
Linux
OS X
Windows

Linux

hosted

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

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

yes

APIs and other access methods

gRPC
JSON over HTTP

ADO.NET
JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

CLI Client
JDBC
ODBC

Supported programming languages

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

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

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

Lua

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

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

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

Interbase Change Views

Multi-source replication
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

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

fine grained access rights according to SQL-standard

simple password-based access control and ACL

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.