DBMS > Cloudflare Workers KV vs. Google Cloud Firestore vs. Snowflake vs. Splunk vs. YottaDB

System Properties Comparison Cloudflare Workers KV vs. Google Cloud Firestore vs. Snowflake vs. Splunk vs. YottaDB

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.

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Cloud-based data warehousing service for structured and semi-structured data

Analytics Platform for Big Data

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Relational DBMS

using the Octo plugin

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

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

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

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

firebase.google.com/products/firestore

www.snowflake.com

www.splunk.com

yottadb.com

Technical documentation

developers.cloudflare.com/kv/api

firebase.google.com/docs/firestore

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

yottadb.com/resources/documentation

Developer

Cloudflare

Google

Snowflake Computing Inc.

Splunk Inc.

YottaDB, LLC

Initial release

2018

2017

2014

2003

2001

License

Commercial or Open Source

commercial

Limited free edition and free developer edition available

Open Source

AGPL 3.0

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

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Docker
Linux

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

by using the Octo plugin

APIs and other access methods

HTTP REST
Proprietary protocol

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

CLI Client
JDBC
ODBC

HTTP REST

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
C++
Dart
JavaScript
Kotlin
Python
Rust
Scala

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

user defined functions

yes

Triggers

yes, with Cloud Functions

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

optimistic locking

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.

yes

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users and roles

Users and groups based on OS-security mechanisms

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.