DBMS > Datomic vs. Google Cloud Datastore vs. Informix vs. SQLite vs. YDB

System Properties Comparison Datomic vs. Google Cloud Datastore vs. Informix vs. SQLite vs. YDB

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

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

A secure embeddable database from IBM, positioned besides IBM Db2 as a relatively low-cost product optimized for OLTP and Internet of Things data

Widely used embeddable, in-process RDBMS

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Document store

Relational DBMS

Since Version 12.10 support for JSON/BSON datatypes compatible with MongoDB

Relational DBMS

Document store
Relational DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS

with Informix TimeSeries Extension

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	17.87
Rank	#35	Overall
	#22	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

www.datomic.com

cloud.google.com/datastore

www.ibm.com/products/informix

www.sqlite.org

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

docs.datomic.com

cloud.google.com/datastore/docs

informix.hcldoc.com
www.ibm.com/support/knowledgecenter/SSGU8G/welcomeIfxServers.html

www.sqlite.org/docs.html

ydb.tech/en/docs

Developer

Cognitect

Google

IBM, HCL Technologies

Effective May 1st, 2017, HCL took on development, technical support, and product management teams, and works jointly with IBM on product strategy, marketing, and sales.

Dwayne Richard Hipp

Yandex

Initial release

2012

2008

1984

2000

2019

Current release

1.0.6735, June 2023

14.10.FC5, November 2020

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

free developer edition available

Open Source

Public Domain

Open Source

Apache 2.0; commercial license available

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, C++ and Java

Server operating systems

All OS with a Java VM

hosted

AIX
HP-UX
Linux
macOS
Solaris
Windows

server-less

Linux

Data scheme

yes

schema-free

yes

dynamic column types

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

yes

yes, details here

yes

Since Version 12.10 support for JSON/BSON datatypes

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

SQL-like query language (YQL)

APIs and other access methods

RESTful HTTP API

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

JDBC
JSON API

MongoDB compatible
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

Clojure
Java

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

.Net
C
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

using Google App Engine

yes

Triggers

By using transaction functions

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

none

Active-passive shard replication

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.

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

via file-system locks

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

yes

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users with fine-grained authentication, authorization, and auditing controls

Access rights defined for Yandex Cloud users

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.