DBMS > Cubrid vs. Datomic vs. EsgynDB vs. Google Cloud Datastore

System Properties Comparison Cubrid vs. Datomic vs. EsgynDB vs. Google Cloud Datastore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Primary database model

Relational DBMS

Document store

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Website

cubrid.com (korean)
cubrid.org (english)

www.datomic.com

www.esgyn.cn

cloud.google.com/datastore

Technical documentation

cubrid.org/manuals

docs.datomic.com

cloud.google.com/datastore/docs

Developer

CUBRID Corporation, CUBRID Foundation

Cognitect

Esgyn

Google

Initial release

2008

2012

2015

2008

Current release

11.0, January 2021

1.0.6735, June 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

limited edition free

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

C, C++, Java

Java, Clojure

C++, Java

Server operating systems

Linux
Windows

All OS with a Java VM

Linux

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

yes

SQL-like query language (GQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP API

ADO.NET
JDBC
ODBC

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

Supported programming languages

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

Clojure
Java

All languages supporting JDBC/ODBC/ADO.Net

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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Transaction Functions

Java Stored Procedures

using Google App Engine

Triggers

yes

By using transaction functions

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

But extensive use of caching in the application peers

Multi-source replication between multi datacenters

Multi-source replication using Paxos

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

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.

Foreign keys

Referential integrity

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

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)

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

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

Zoona Case Study
16 December 2017, AWS Blog

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

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

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

Why Google will waive egress fees for customers ditching GCP
11 January 2024, The Register

provided by Google News

Share this page