DBMS > AnzoGraph DB vs. JaguarDB vs. KeyDB vs. Snowflake

System Properties Comparison AnzoGraph DB vs. JaguarDB vs. KeyDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

Performant, highly scalable DBMS for AI and IoT applications

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

Graph DBMS
RDF store

Key-value store
Vector DBMS

Key-value store

Relational DBMS

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

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

cambridgesemantics.com/anzograph

www.jaguardb.com

github.com/Snapchat/KeyDB
keydb.dev

www.snowflake.com

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

www.jaguardb.com/support.html

docs.keydb.dev

docs.snowflake.net/manuals/index.html

Developer

Cambridge Semantics

DataJaguar, Inc.

EQ Alpha Technology Ltd.

Snowflake Computing Inc.

Initial release

2018

2015

2019

2014

Current release

2.3, January 2021

3.3 July 2023

License

Commercial or Open Source

commercial

free trial version available

Open Source

GPL V3.0

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

the server part. Clients available in other languages

C++

Server operating systems

Linux

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

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.

yes

Secondary indexes

yes

by using the Redis Search module

SQL

Support of SQL

SPARQL and SPARQL* as primary query language. Cypher preview.

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
Python

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

user defined functions and aggregates

Lua

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

Multi-source replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Eventual Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

not needed 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

Access rights for users and roles

rights management via user accounts

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.