DBMS > Bangdb vs. Geode vs. Snowflake vs. TigerGraph

System Properties Comparison Bangdb vs. Geode vs. Snowflake vs. TigerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store
Graph DBMS
Time Series DBMS

Key-value store

Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS

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

Score	0.16
Rank	#338	Overall
	#47	Document stores
	#32	Graph DBMS
	#31	Time Series DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

Technical documentation

docs.bangdb.com

geode.apache.org/docs

docs.snowflake.net/manuals/index.html

docs.tigergraph.com

Developer

Sachin Sinha, BangDB

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Snowflake Computing Inc.

Initial release

2012

2002

2014

2017

Current release

BangDB 2.0, October 2021

1.1, February 2017

License

Commercial or Open Source

Open Source

BSD 3

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java

C++

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

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

secondary, composite, nested, reverse, geospatial

SQL

Support of SQL

SQL like support with command line tool

SQL-like query language (OQL)

yes

SQL-like query language (GSQL)

APIs and other access methods

Proprietary protocol
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Java
Python

.Net
All JVM based languages
C++
Groovy
Java
Scala

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes, Notifications (with Streaming only)

yes

Cache Event Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, run db with in-memory only mode

yes

User concepts

Access control

yes (enterprise version only)

Access rights per client and object definable

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

Role-based access control

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.