DBMS > Cloudflare Workers KV vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. OrientDB

System Properties Comparison Cloudflare Workers KV vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. OrientDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A global, low-latency, key-value store for applications on Cloudflare with exceptionally high read volumes and low-latency.

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

Globally distributed, horizontally scalable, multi-model database service

Multi-model DBMS (Document, Graph, Key/Value)

Primary database model

Key-value store

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Graph DBMS
Key-value store

Secondary database models

Spatial DBMS

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

Score	0.39
Rank	#274	Overall
	#39	Key-value stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Website

www.cloudflare.com/developer-platform/workers-kv

cloud.google.com/datastore

azure.microsoft.com/services/cosmos-db

orientdb.org

Technical documentation

developers.cloudflare.com/kv/api

cloud.google.com/datastore/docs

learn.microsoft.com/azure/cosmos-db

www.orientdb.com/docs/last/index.html

Developer

Cloudflare

Google

Microsoft

OrientDB LTD; CallidusCloud; SAP

Initial release

2018

2008

2014

2010

Current release

3.2.29, March 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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

Server operating systems

hosted

All OS with a Java JDK (>= JDK 6)

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

Typing

predefined data types such as float or date

yes, details here

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

SQL-like query language, no joins

APIs and other access methods

HTTP REST
Proprietary protocol

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

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

Supported programming languages

C
C++
Dart
JavaScript
Kotlin
Python
Rust
Scala

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Server-side scripts

Stored procedures

using Google App Engine

JavaScript

Java, Javascript

Triggers

Callbacks using the Google Apps Engine

JavaScript

Hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

Implicit feature of the cloud service

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

relationship in graphs

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Multi-item ACID transactions with snapshot isolation within a partition

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.

User concepts

Access control

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

Access rights can be defined down to the item level

Access rights for users and roles; record level security configurable

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.