DBMS > Apache Phoenix vs. Blazegraph vs. Kyligence Enterprise vs. Snowflake

System Properties Comparison Apache Phoenix vs. Blazegraph vs. Kyligence Enterprise vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

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

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

A distributed analytics engine for big data, built on top of Apache Kylin

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

Primary database model

Relational DBMS

Graph DBMS
RDF store

Relational DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	0.40
Rank	#269	Overall
	#124	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

phoenix.apache.org

blazegraph.com

kyligence.io/kyligence-enterprise

www.snowflake.com

Technical documentation

phoenix.apache.org

wiki.blazegraph.com

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Blazegraph

Kyligence, Inc.

Snowflake Computing Inc.

Initial release

2014

2006

2016

2014

Current release

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

2.1.5, March 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

extended commercial license available

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

Java

Server operating systems

Linux
Unix
Windows

Linux
OS X
Windows

Linux

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

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

Typing

predefined data types such as float or date

yes

RDF literal types

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

SPARQL is used as query language

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

JDBC

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

Transaction concepts

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

ACID

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

Security and Authentication via Web Application Container (Tomcat, Jetty)

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.