DBMS > FatDB vs. Google Cloud Datastore vs. JanusGraph vs. NSDb

System Properties Comparison FatDB vs. Google Cloud Datastore vs. JanusGraph vs. NSDb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Document store
Key-value store

Document store

Graph DBMS

Time Series DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

cloud.google.com/datastore

janusgraph.org

nsdb.io

Technical documentation

cloud.google.com/datastore/docs

docs.janusgraph.org

nsdb.io/Architecture

Developer

FatCloud

Google

Linux Foundation; originally developed as Titan by Aurelius

Initial release

2012

2008

2017

Current release

0.6.3, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.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

Java

Java, Scala

Server operating systems

Windows

hosted

Linux
OS X
Unix
Windows

Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

gRPC
HTTP REST
WebSocket

Supported programming languages

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

Clojure
Java
Python

Java
Scala

Server-side scripts

Stored procedures

yes

via applications

using Google App Engine

yes

Triggers

yes

via applications

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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.

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

Using Apache Lucene

In-memory capabilities

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

User concepts

Access control

Can implement custom security layer via applications

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

User authentification and security via Rexster Graph Server

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

Best cloud storage of 2024
21 May 2024, TechRadar

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

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

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

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

provided by Google News

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

Database Deep Dives: JanusGraph
8 August 2019, IBM

From graph db to graph embedding. In 7 simple steps. | by Andy Greatorex
30 July 2020, Towards Data Science

Compose for JanusGraph arrives on Bluemix
15 September 2017, IBM

Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph
3 October 2019, The New Stack

provided by Google News

Share this page