DBMS > Datomic vs. Google Cloud Datastore vs. Microsoft Azure AI Search vs. SAP HANA

System Properties Comparison Datomic vs. Google Cloud Datastore vs. Microsoft Azure AI Search vs. SAP HANA

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

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

Search-as-a-service for web and mobile app development

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Vector DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.55
Rank	#144	Overall
	#67	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	5.75
Rank	#58	Overall
	#7	Search engines

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

www.datomic.com

cloud.google.com/datastore

azure.microsoft.com/en-us/services/search

www.sap.com/products/hana.html

Technical documentation

docs.datomic.com

cloud.google.com/datastore/docs

learn.microsoft.com/en-us/azure/search

help.sap.com/hana

Developer

Cognitect

Google

Microsoft

SAP

Initial release

2012

2008

2015

2010

Current release

1.0.7180, July 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

limited edition free

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Clojure

Server operating systems

All OS with a Java VM

hosted

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

APIs and other access methods

RESTful HTTP API

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

RESTful HTTP API

JDBC
ODBC

Supported programming languages

Clojure
Java

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

C#
Java
JavaScript
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

using Google App Engine

SQLScript, R

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

Implicit feature of the cloud service

yes

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

yes

Implicit feature of the cloud service

yes

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

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)

yes

using Azure authentication

yes

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.