DBMS > AllegroGraph vs. EsgynDB vs. GridDB vs. Snowflake

System Properties Comparison AllegroGraph vs. EsgynDB vs. GridDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance, persistent RDF store with additional support for Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Scalable in-memory time series database optimized for IoT and Big Data

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

Primary database model

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Key-value store
Relational DBMS

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

Score	1.13
Rank	#179	Overall
	#30	Document stores
	#17	Graph DBMS
	#7	RDF stores
	#7	Vector DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

franz.com/agraph/support/documentation/current/agraph-introduction.html

docs.griddb.net

docs.snowflake.net/manuals/index.html

Developer

Franz Inc.

Esgyn

Toshiba Corporation

Snowflake Computing Inc.

Initial release

2004

2015

2013

2014

Current release

8.0, December 2023

5.1, August 2022

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also 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

C++, Java

C++

Server operating systems

Linux
OS X
Windows

Linux

hosted

Data scheme

yes

RDF schemas

yes

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

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

bulk load of XML files possible

yes

Secondary indexes

yes

SQL

Support of SQL

SPARQL is used as query language

yes

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

RESTful HTTP API
SPARQL

ADO.NET
JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

All languages supporting JDBC/ODBC/ADO.Net

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

JavaScript or Common Lisp

Java Stored Procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

with Federation

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID at container level

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

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

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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

More information provided by the system vendor

Specific characteristics

Knowledge Graph Platform Leader FedShard - Designed for Entity-Event Knowledge Graph...
» more

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

AllegroGraph is uniquely suited to support adhoc queries through SPARQL, Prolog and...
» more

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

News

How a Neuro-Symbolic AI Approach Can Improve Trust in AI Apps
23 May 2024

Can Neuro-Symbolic AI Solve AI’s Weaknesses?
17 April 2024

100 Companies That Matter in KM – Franz Inc.
3 April 2024

Exploring AllegroGraph v8 – Unleashing the Power of Neuro-Symbolic AI (Recorded Webinar)
9 February 2024

What is Neuro-Symbolic AI?
23 January 2024

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.