DBMS > Blazegraph vs. KeyDB vs. Kyligence Enterprise vs. Snowflake

System Properties Comparison Blazegraph vs. KeyDB 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

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

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

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

Graph DBMS
RDF store

Key-value store

Relational DBMS

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

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

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

Score	0.40
Rank	#269	Overall
	#124	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

blazegraph.com

github.com/Snapchat/KeyDB
keydb.dev

kyligence.io/kyligence-enterprise

www.snowflake.com

Technical documentation

wiki.blazegraph.com

docs.keydb.dev

docs.snowflake.net/manuals/index.html

Developer

Blazegraph

EQ Alpha Technology Ltd.

Kyligence, Inc.

Snowflake Computing Inc.

Initial release

2006

2019

2016

2014

Current release

2.1.5, March 2019

License

Commercial or Open Source

Open Source

extended commercial license available

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

Java

C++

Java

Server operating systems

Linux
OS X
Windows

Linux

hosted

Data scheme

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

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.

yes

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

SPARQL is used as query language

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
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

Lua

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

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Strong eventual consistency with CRDTs

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

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

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

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.