DBMS > FatDB vs. Google Cloud Datastore vs. Kyligence Enterprise vs. OushuDB vs. Yaacomo

System Properties Comparison FatDB vs. Google Cloud Datastore vs. Kyligence Enterprise vs. OushuDB vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines 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 distributed analytics engine for big data, built on top of Apache Kylin

A data warehouse powered by Apache HAWQ supporting descriptive analysis and advanced machine learning

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Document store

Relational DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.40
Rank	#269	Overall
	#124	Relational DBMS

Score	0.04
Rank	#363	Overall
	#154	Relational DBMS

Website

cloud.google.com/datastore

kyligence.io/kyligence-enterprise

www.oushu.com/product/oushuDB

yaacomo.com

Technical documentation

cloud.google.com/datastore/docs

www.oushu.com/documentation

Developer

FatCloud

Google

Kyligence, Inc.

Oushu

Q2WEB GmbH

Initial release

2012

2008

2016

2009

Current release

4.0.1, August 2020

License

Commercial or Open Source

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

Java

Server operating systems

Windows

hosted

Linux

Android
Linux
Windows

Data scheme

schema-free

yes

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

Via inetgration in SQL Server

SQL-like query language (GQL)

ANSI SQL for queries (using Apache Calcite)

Full-featured ANSI SQL support

yes

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

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

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

C
C++

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Hadoop integration

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.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

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

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)

Kerberos, SSL and role based access

fine grained access rights according to SQL-standard

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

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

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

provided by Google News

Kyligence Grows OLAP Business in the Cloud
20 February 2020, Datanami

Kyligence adds ClickHouse OLAP engine to its analytics platform
10 August 2021, VentureBeat

Distributed OLAPer Kyligence accelerates core engine, adds real-time data support – Blocks and Files
10 August 2021, Blocks & Files

How Kyligence Cloud uses Amazon EMR Serverless to simplify OLAP | Amazon Web Services
9 November 2022, AWS Blog

The 10 Hottest Big Data Tools Of 2023
23 November 2023, CRN

provided by Google News

China's answer to Snowflake is shaping as data demands upgrade
8 September 2021, PingWest

provided by Google News

Share this page