DBMS > Bangdb vs. Google Cloud Datastore vs. RDF4J vs. SwayDB

System Properties Comparison Bangdb vs. Google Cloud Datastore vs. RDF4J vs. SwayDB

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store
Graph DBMS
Time Series DBMS

Document store

RDF store

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

bangdb.com

cloud.google.com/datastore

rdf4j.org

swaydb.simer.au

Technical documentation

docs.bangdb.com

cloud.google.com/datastore/docs

rdf4j.org/documentation

Developer

Sachin Sinha, BangDB

Google

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Simer Plaha

Initial release

2012

2008

2004

2018

Current release

BangDB 2.0, October 2021

License

Commercial or Open Source

Open Source

BSD 3

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

GNU Affero GPL V3.0

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

Scala

Server operating systems

Linux

hosted

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

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

yes, details here

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.

Secondary indexes

yes

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

SQL-like query language (GQL)

APIs and other access methods

Proprietary protocol
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

C
C#
C++
Java
Python

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
PHP
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

using Google App Engine

yes

Triggers

yes, Notifications (with Streaming only)

Callbacks using the Google Apps Engine

yes

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Isolation support depends on the API used

Atomic execution of operations

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 storage is supported 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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
29 April 2024, TechRadar

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

GraphDB Goes Open Source
27 January 2020, iProgrammer

Ontotext's GraphDB 8.10 Makes Knowledge Graph Experience Faster and Richer
13 June 2019, Markets Insider

provided by Google News

Share this page