DBMS > EsgynDB vs. Google Cloud Bigtable vs. TerarkDB vs. TimescaleDB

System Properties Comparison EsgynDB vs. Google Cloud Bigtable vs. TerarkDB vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

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

Primary database model

Relational DBMS

Key-value store
Wide column store

Key-value store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	2.97
Rank	#92	Overall
	#15	Key-value stores
	#8	Wide column stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Website

www.esgyn.cn

cloud.google.com/bigtable

github.com/bytedance/terarkdb

www.timescale.com

Technical documentation

cloud.google.com/bigtable/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.timescale.com

Developer

Esgyn

Google

ByteDance, originally Terark

Timescale

Initial release

2015

2016

2017

Current release

2.15.0, May 2024

License

Commercial or Open Source

commercial

restricted open source version available

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++

Server operating systems

Linux

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

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

full PostgreSQL SQL syntax

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

C++ API
Java API

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

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Go
Java
JavaScript (Node.js)
Python

C++
Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

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

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

Internal replication in Colossus, and regional replication between two clusters in different zones

none

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

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

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

Access rights for users, groups and roles based on Google Cloud Identity and 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.

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 adds graph processing to Spanner, SQL support to Bigtable
1 August 2024, InfoWorld

Google introduces Bigtable SQL access and Spanner's new AI-ready features
1 August 2024, ZDNet

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Google Cloud Adds GenAI, Core Enhancements Across Data Platform
1 August 2024, The New Stack

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

provided by Google News

General availability: Latest version of the TimeScaleDB extension on Azure Database for PostgreSQL - Flexible Server
8 May 2024, Microsoft

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

PostgreSQL is Now Faster than Pinecone, 75% Cheaper, with New Open Source Extensions
11 June 2024, PR Newswire

TimescaleDB goes distributed; implements ‘Chunking’ over ‘Sharding’ for scaling-out
22 August 2019, Packt Hub

provided by Google News

Share this page