DBMS > Apache Phoenix vs. etcd vs. Snowflake vs. YottaDB

System Properties Comparison Apache Phoenix vs. etcd vs. Snowflake vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

A distributed reliable key-value store

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

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

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

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

phoenix.apache.org

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

www.snowflake.com

yottadb.com

Technical documentation

phoenix.apache.org

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

docs.snowflake.net/manuals/index.html

yottadb.com/resources/documentation

Developer

Apache Software Foundation

Snowflake Computing Inc.

YottaDB, LLC

Initial release

2014

2001

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

3.4, August 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

commercial

Open Source

AGPL 3.0

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

Server operating systems

Linux
Unix
Windows

FreeBSD
Linux
Windows

experimental

hosted

Docker
Linux

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

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

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

by using the Octo plugin

APIs and other access methods

JDBC

gRPC
JSON over HTTP

CLI Client
JDBC
ODBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

JavaScript (Node.js)
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

Triggers

yes, watching key changes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

Users and groups based on OS-security mechanisms

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.