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

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

Editorial information provided by DB-Engines

Name

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

An open source graph database built for real-time streaming and compatible with Neo4j

Primary database model

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

Score	3.02
Rank	#98	Overall
	#8	Graph DBMS

Website

aws.amazon.com/redshift

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

cloud.google.com/datastore

google.github.io/lovefield

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

memgraph.com/docs

Social network pages

Developer

Amazon (based on PostgreSQL)

Cloudflare

Google

Memgraph Ltd

Initial release

2012

2018

2008

2014

2017

Current release

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSL 1.1; commercial license for enterprise edition 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

JavaScript

C and C++

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 and schema-optional

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

Bolt protocol
Cypher query language

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

.Net
C
C++
Elixir
Go
Haskell
Java
JavaScript
PHP
Python
Ruby
Scala

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

dynamic graph partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

none

Multi-source replication using RAFT

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

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

yes

relationships 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

ACID

with snapshot isolation

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

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

yes

with periodic snapshot and write-ahead logging (WAL) of changes

In-memory capabilities

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

yes

using MemoryDB

yes

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)

Users, roles and permissions

More information provided by the system vendor

Specific characteristics

Memgraph directly connects to your streaming infrastructure so you and your team...
» more

Competitive advantages

Business Source License ensures a future for the Memgraph community MAGE algorithm...
» more

Typical application scenarios

Graph algorithms in bioinformatics Social network analysis Cryptocurrency network...
» more

Licensing and pricing models

You can check out our pricing model and licenses on the company website .
» more

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.