DBMS > EsgynDB vs. FatDB vs. Galaxybase vs. Google BigQuery vs. TimescaleDB

System Properties Comparison EsgynDB vs. FatDB vs. Galaxybase vs. Google BigQuery vs. TimescaleDB

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Scalable, ACID-compliant native distributed parallel graph platform

Large scale data warehouse service with append-only tables

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Document store
Key-value store

Graph DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

www.esgyn.cn

galaxybase.com

cloud.google.com/bigquery

www.timescale.com

Technical documentation

cloud.google.com/bigquery/docs

docs.timescale.com

Developer

Esgyn

FatCloud

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Google

Timescale

Initial release

2015

2012

2017

2010

2017

Current release

Nov 20, November 2021

2.13.0, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache 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

C++, Java

C and Java

Server operating systems

Linux

Windows

Linux

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

Strong typed schema

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

full PostgreSQL SQL syntax

APIs and other access methods

ADO.NET
JDBC
ODBC

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

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Go
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

yes

via applications

user defined procedures and functions

user defined functions

in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

selectable replication factor

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

Role-based access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.