DBMS > Datomic vs. EsgynDB vs. Google Cloud Bigtable vs. Postgres-XL

System Properties Comparison Datomic vs. EsgynDB vs. Google Cloud Bigtable vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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.

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Relational DBMS

Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Website

www.datomic.com

www.esgyn.cn

cloud.google.com/bigtable

www.postgres-xl.org

Technical documentation

docs.datomic.com

cloud.google.com/bigtable/docs

www.postgres-xl.org/documentation

Developer

Cognitect

Esgyn

Google

Initial release

2012

2015

2014

since 2012, originally named StormDB

Current release

1.0.7075, December 2023

10 R1, October 2018

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

Mozilla public license

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, Clojure

C++, Java

Server operating systems

All OS with a Java VM

Linux

hosted

Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

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

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

Supported programming languages

Clojure
Java

All languages supporting JDBC/ODBC/ADO.Net

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

Java Stored Procedures

user defined functions

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication between multi datacenters

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

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

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

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

Stanchion Turns SQLite Into A Column Store
15 February 2024, iProgrammer

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Brazil’s Nubank acquires US software firm Cognitect, creator of Clojure and Datomic
24 July 2020, LatamList

provided by Google News

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

Google scales up Cloud Bigtable NoSQL database
27 January 2022, TechTarget

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google Cloud makes it cheaper to run smaller workloads on Bigtable
7 April 2020, TechCrunch

Google introduces Cloud Bigtable managed NoSQL database to process data at scale
6 May 2015, VentureBeat

provided by Google News

Share this page