DBMS > BigObject vs. FatDB vs. Google Cloud Datastore vs. Microsoft Azure Table Storage

System Properties Comparison BigObject vs. FatDB vs. Google Cloud Datastore vs. Microsoft Azure Table Storage

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

Analytic DBMS for real-time computations and queries

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 Wide Column Store for rapid development using massive semi-structured datasets

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store
Key-value store

Document store

Wide column store

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Website

bigobject.io

cloud.google.com/datastore

azure.microsoft.com/en-us/services/storage/tables

Technical documentation

docs.bigobject.io

cloud.google.com/datastore/docs

Developer

BigObject, Inc.

FatCloud

Google

Microsoft

Initial release

2015

2012

2008

2012

License

Commercial or Open Source

commercial

free community edition 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

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Windows

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

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

SQL

Support of SQL

SQL-like DML and DDL statements

Via inetgration in SQL Server

SQL-like query language (GQL)

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

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

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

RESTful HTTP API

Supported programming languages

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

yes

via applications

using Google App Engine

Triggers

yes

via applications

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Multi-source replication using Paxos

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

none

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.

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

Can implement custom security layer via applications

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

Access rights based on private key authentication or shared access signatures

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 Platform: Professional Data Engineer certification prep
11 June 2024, oreilly.com

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

Best cloud storage of 2024
4 June 2024, TechRadar

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

provided by Google News

Working with Azure to Use and Manage Data Lakes
7 March 2024, Simplilearn

How to Use C# Azure.Data.Tables SDK with Azure Cosmos DB
9 July 2021, hackernoon.com

How to use Azure Table storage in .Net
14 January 2019, InfoWorld

Quick Guide to Azure Storage Pricing
16 May 2023, DevOps.com

How to write data to Azure Table Store with an Azure Function
14 April 2017, Experts Exchange

provided by Google News

Share this page