DBMS > Amazon Redshift vs. Cloudflare Workers KV vs. Google Cloud Datastore vs. Lovefield vs. Sqrrl

System Properties Comparison Amazon Redshift vs. Cloudflare Workers KV vs. Google Cloud Datastore vs. Lovefield vs. Sqrrl

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

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

Embeddable relational database for web apps written in pure JavaScript

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.32
Rank	#283	Overall
	#40	Key-value stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Website

aws.amazon.com/redshift

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

cloud.google.com/datastore

google.github.io/lovefield

sqrrl.com

Technical documentation

docs.aws.amazon.com/redshift

developers.cloudflare.com/kv/api

cloud.google.com/datastore/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Amazon (based on PostgreSQL)

Cloudflare

Google

Amazon

originally Sqrrl Data, Inc.

Initial release

2012

2018

2008

2014

2012

Current release

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

JavaScript

Java

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux

Data scheme

yes

schema-free

yes

schema-free

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (GQL)

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

JDBC
ODBC

HTTP REST
Proprietary protocol

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

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Dart
JavaScript
Kotlin
Python
Rust
Scala

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

JavaScript

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in Python

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

none

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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.

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

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)

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.