DBMS > Cloudflare Workers KV vs. FoundationDB vs. Microsoft SQL Server vs. Teradata Aster

System Properties Comparison Cloudflare Workers KV vs. FoundationDB vs. Microsoft SQL Server vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

Ordered key-value store. Core features are complimented by layers.

Microsofts flagship relational DBMS

Platform for big data analytics on multistructured data sources and types

Primary database model

Key-value store

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

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

Score	1.07
Rank	#188	Overall
	#31	Document stores
	#28	Key-value stores
	#86	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

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

github.com/apple/foundationdb

www.microsoft.com/en-us/sql-server

Technical documentation

developers.cloudflare.com/kv/api

apple.github.io/foundationdb

learn.microsoft.com/en-US/sql/sql-server

Developer

Cloudflare

FoundationDB

Microsoft

Teradata

Initial release

2018

2013

1989

2005

Current release

6.2.28, November 2020

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

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

C++

Server operating systems

hosted

Linux
OS X
Windows

Linux
Windows

Linux

Data scheme

schema-free

some layers support schemas

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

some layers support typing

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

supported in specific SQL layer only

yes

APIs and other access methods

HTTP REST
Proprietary protocol

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C
C++
Dart
JavaScript
Kotlin
Python
Rust
Scala

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

in SQL-layer only

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, but depending on the SQL-Server Edition

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Linearizable consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

in SQL-layer only

yes

Transaction concepts

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

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.